public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
To: jikos@kernel.org
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jiri Slaby (SUSE)" <jirislaby@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: [PATCH 3/7] HID: protect hid_device::bpf by CONFIG_HID_BPF
Date: Thu,  1 Feb 2024 12:53:16 +0100	[thread overview]
Message-ID: <20240201115320.684-4-jirislaby@kernel.org> (raw)
In-Reply-To: <20240201115320.684-1-jirislaby@kernel.org>

And not by CONFIG_BPF. BPF can be selected while HID_BPF does not have
to. It actually cannot be on some platforms due to Kconfig dependences.

This saves quite some bytes on those setups.

Found by https://github.com/jirislaby/clang-struct.

Signed-off-by: Jiri Slaby (SUSE) <jirislaby@kernel.org>
Cc: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
---
 include/linux/hid.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/hid.h b/include/linux/hid.h
index 7c26db874ff0..b12cb1c8e682 100644
--- a/include/linux/hid.h
+++ b/include/linux/hid.h
@@ -683,9 +683,9 @@ struct hid_device {							/* device report descriptor */
 
 	unsigned int id;						/* system unique id */
 
-#ifdef CONFIG_BPF
+#ifdef CONFIG_HID_BPF
 	struct hid_bpf bpf;						/* hid-bpf data */
-#endif /* CONFIG_BPF */
+#endif /* CONFIG_HID_BPF */
 };
 
 void hiddev_free(struct kref *ref);
-- 
2.43.0


  parent reply	other threads:[~2024-02-01 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 11:53 [PATCH 0/7] HID: unused struct members cleanup Jiri Slaby (SUSE)
2024-02-01 11:53 ` [PATCH 1/7] HID: apple: remove unused members from struct apple_sc_backlight Jiri Slaby (SUSE)
2024-02-14 12:54   ` Aditya Garg
2024-02-01 11:53 ` [PATCH 2/7] HID: wacom: remove unused hid_data::pressure Jiri Slaby (SUSE)
2024-02-02  2:30   ` Ping Cheng
2024-02-01 11:53 ` Jiri Slaby (SUSE) [this message]
2024-02-01 11:53 ` [PATCH 4/7] HID: hid-lg3ff: remove unused struct lg3ff_device Jiri Slaby (SUSE)
2024-02-01 11:53 ` [PATCH 5/7] HID: hid-multitouch: remove unused mt_application::dev_time Jiri Slaby (SUSE)
2024-02-01 11:53 ` [PATCH 6/7] HID: hid-prodikeys: remove unused struct pcmidi_snd members Jiri Slaby (SUSE)
2024-02-01 11:53 ` [PATCH 7/7] HID: hid-prodikeys: remove struct pk_device Jiri Slaby (SUSE)
2024-02-13 10:44 ` [PATCH 0/7] HID: unused struct members cleanup Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240201115320.684-4-jirislaby@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox