Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit dfc02f81 authored by Neill Kapron's avatar Neill Kapron
Browse files

BPF: rename bpf_defaults to bpf_cc_defaults 



With the addition of defaults to the bpf soong module (see aosp/3249485
), the name `bpf_defaults` will be used to define defaults for bpf
program compilation. While there are separate soong namespaces for
module types and module names, rename the existing bpf_defaults
cc_defaults to bpf_cc_defaults for clarity.

While we're at it, add -Wextra, and cleanup unnecessary cflags in
clauses which use bpf_cc_defaults.

Test: TH
Change-Id: Ib5f453ce33b13c698e8b91088bc59f8c6719c892
Signed-off-by: default avatarNeill Kapron <nkapron@google.com>
parent aa8ceca8

docs/tidy.md

+2 −2
Original line number Diff line number Diff line
@@ -38,7 +38,7 @@ For example, in 
clang-tidy is enabled explicitly and with a different check list:

```

cc_defaults {

    name: "bpf_defaults",

    name: "bpf_cc_defaults",

    // snipped

    tidy: true,

    tidy_checks: [
@@ -52,7 +52,7 @@ cc_defaults { 
}

```

That means in normal builds, even without `WITH_TIDY=1`,

the modules that use `bpf_defaults` _should_ run clang-tidy

the modules that use `bpf_cc_defaults` _should_ run clang-tidy

over C/C++ source files with the given `tidy_checks`.



However since clang-tidy warnings and its runtime cost might