From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Pali Rohár" <pali@kernel.org>
Subject: [PATCH v1 0/4] Input: Increase size of phys in the drivers
Date: Fri, 28 Feb 2025 14:07:43 +0200 [thread overview]
Message-ID: <20250228121147.242115-1-andriy.shevchenko@linux.intel.com> (raw)
The drivers are using local member of 32 bytes to hold up to 40 (one-byte)
characters. GCC complains on that. This series fixes the issue in the affected
input drivers. Note, this is currently the biggest part of the warnings that
are being treated as errors with the default configurations on x86. With this
being applied we become quite close to enable CONFIG_WERROR=y (which is default
and basically reverted) in CIs. Clang, OTOH, has currently no issues with that.
Andy Shevchenko (4):
Input: ALPS - increase size of phys2 and phys3
Input: atkbd - increase size of phys
Input: lifebook - increase size of phys
Input: psmouse - increase size of phys
drivers/input/keyboard/atkbd.c | 2 +-
drivers/input/mouse/alps.h | 4 ++--
drivers/input/mouse/lifebook.c | 2 +-
drivers/input/mouse/psmouse.h | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
--
2.47.2
next reply other threads:[~2025-02-28 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 12:07 Andy Shevchenko [this message]
2025-02-28 12:07 ` [PATCH v1 1/4] Input: ALPS - increase size of phys2 and phys3 Andy Shevchenko
2025-02-28 12:07 ` [PATCH v1 2/4] Input: atkbd - increase size of phys Andy Shevchenko
2025-02-28 12:07 ` [PATCH v1 3/4] Input: lifebook " Andy Shevchenko
2025-02-28 12:07 ` [PATCH v1 4/4] Input: psmouse " Andy Shevchenko
2025-02-28 12:52 ` [PATCH v1 0/4] Input: Increase size of phys in the drivers Andy Shevchenko
2025-03-04 12:14 ` Andy Shevchenko
2025-03-05 7:18 ` Dmitry Torokhov
2025-03-05 10:06 ` Andy Shevchenko
2025-03-26 9:48 ` Andy Shevchenko
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=20250228121147.242115-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@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
all inboxes | Powered by JetHome®