diff options
author | Miguel Ojeda <[email protected]> | 2024-07-09 18:05:58 +0200 |
---|---|---|
committer | Miguel Ojeda <[email protected]> | 2024-07-10 10:28:51 +0200 |
commit | f85bea18f71b2817ea45d63c6d1b91f9bc4a811f (patch) | |
tree | a83e5b3a5d267a5bc8704eeccf320e9a72715ee8 /tools/perf/util/trace-event-scripting.c | |
parent | dee1396a486cf2b6e7840322f6d104680649f2ff (diff) |
rust: allow `dead_code` for never constructed bindings
Starting with the upcoming Rust 1.80.0 (since upstream commit 35130d7233e9
("Detect pub structs never constructed and unused associated constants
in traits")), the `dead_code` pass detects more cases, which triggers
in the `bindings` crate:
warning: struct `boot_params` is never constructed
--> rust/bindings/bindings_generated.rs:10684:12
|
10684 | pub struct boot_params {
| ^^^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
As well as in the `uapi` one:
warning: struct `boot_params` is never constructed
--> rust/uapi/uapi_generated.rs:10392:12
|
10392 | pub struct boot_params {
| ^^^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
These are all expected, since we do not use all the structs in the
bindings that `bindgen` generates from the C headers.
Therefore, allow them.
Reviewed-by: Björn Roy Baron <[email protected]>
Reviewed-by: Finn Behrens <[email protected]>
Tested-by: Benno Lossin <[email protected]>
Tested-by: Andreas Hindborg <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Miguel Ojeda <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions