diff options
| author | 2024-09-13 17:55:12 +0000 | |
|---|---|---|
| committer | 2024-09-13 17:55:12 +0000 | |
| commit | dfc02f81fc90702b6e05c4729002dc77c9fd87cf (patch) | |
| tree | 8abc7ebadc2cbec325f46a207a22f3974a15bd3e /docs/tidy.md | |
| parent | aa8ceca851efaf057df5472dc95fe8eb4b0496e8 (diff) | |
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: Neill Kapron <nkapron@google.com>
Diffstat (limited to 'docs/tidy.md')
| -rw-r--r-- | docs/tidy.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/tidy.md b/docs/tidy.md index ae0ca9360..2e4c9579d 100644 --- a/docs/tidy.md +++ b/docs/tidy.md @@ -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 |