From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Jorge Lopez" <jorge.lopez2@hp.com>,
"Li Zetao" <lizetao1@huawei.com>,
"Simon Trimmer" <simont@opensource.cirrus.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net,
linux-input@vger.kernel.org
Cc: Corentin Chary <corentin.chary@gmail.com>,
"Luke D. Jones" <luke@ljones.dev>,
Mark Pearson <markpearson@lenovo.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Subject: [PATCH v1 0/7] platform/x86: Move to 2-argument strscpy()
Date: Sun, 2 Jun 2024 11:57:53 +0300 [thread overview]
Message-ID: <20240602090244.1666360-1-andy.shevchenko@gmail.com> (raw)
Move to 2-argument strscpy() to make code shorter and have an additional check.
No functional change intended.
Some cases are let untouched where it looks better with the 3rd argument.
Andy Shevchenko (7):
platform/x86: asus-tf103c-dock: Use 2-argument strscpy()
platform/x86: hp: hp-bioscfg: Use 2-argument strscpy()
platform/x86: intel: chtwc_int33fe: Use 2-argument strscpy()
platform/x86: serial-multi-instantiate: Use 2-argument strscpy()
platform/x86: think-lmi: Use 2-argument strscpy()
platform/x86: thinkpad_acpi: Use 2-argument strscpy()
platform/x86: touchscreen_dmi: Use 2-argument strscpy()
drivers/platform/x86/asus-tf103c-dock.c | 10 +++++-----
.../x86/hp/hp-bioscfg/enum-attributes.c | 18 +++++-------------
.../x86/hp/hp-bioscfg/int-attributes.c | 7 ++-----
.../x86/hp/hp-bioscfg/order-list-attributes.c | 18 +++++-------------
.../x86/hp/hp-bioscfg/passwdobj-attributes.c | 19 +++++--------------
.../x86/hp/hp-bioscfg/spmobj-attributes.c | 3 +--
.../x86/hp/hp-bioscfg/string-attributes.c | 12 ++++--------
drivers/platform/x86/intel/chtwc_int33fe.c | 6 +++---
.../platform/x86/serial-multi-instantiate.c | 4 ++--
drivers/platform/x86/think-lmi.c | 4 ++--
drivers/platform/x86/thinkpad_acpi.c | 6 ++----
drivers/platform/x86/touchscreen_dmi.c | 2 +-
12 files changed, 37 insertions(+), 72 deletions(-)
--
2.45.1
next reply other threads:[~2024-06-02 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 8:57 Andy Shevchenko [this message]
2024-06-02 8:57 ` [PATCH v1 1/7] platform/x86: asus-tf103c-dock: Use 2-argument strscpy() Andy Shevchenko
2024-06-02 13:28 ` Hans de Goede
2024-06-02 8:57 ` [PATCH v1 2/7] platform/x86: hp: hp-bioscfg: " Andy Shevchenko
2024-06-02 8:57 ` [PATCH v1 3/7] platform/x86: intel: chtwc_int33fe: " Andy Shevchenko
2024-06-02 8:57 ` [PATCH v1 4/7] platform/x86: serial-multi-instantiate: " Andy Shevchenko
2024-06-02 8:57 ` [PATCH v1 5/7] platform/x86: think-lmi: " Andy Shevchenko
2024-06-02 8:57 ` [PATCH v1 6/7] platform/x86: thinkpad_acpi: " Andy Shevchenko
2024-06-02 8:58 ` [PATCH v1 7/7] platform/x86: touchscreen_dmi: " Andy Shevchenko
2024-06-03 9:16 ` Hans de Goede
2024-06-03 11:54 ` [PATCH v1 0/7] platform/x86: Move to " Ilpo Järvinen
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=20240602090244.1666360-1-andy.shevchenko@gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jorge.lopez2@hp.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=luke@ljones.dev \
--cc=markpearson@lenovo.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=simont@opensource.cirrus.com \
/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;
as well as URLs for NNTP newsgroup(s).