From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Abdul Rahim <abdul.rahim@myyahoo.com>,
rafael@kernel.org, rui.zhang@intel.com, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: thermal: Use strscpy() instead of strcpy()
Date: Fri, 13 Sep 2024 21:31:57 +0200 [thread overview]
Message-ID: <c4e7b3ac-d8fa-47b9-84f6-e3332bb54e12@wanadoo.fr> (raw)
In-Reply-To: <20240913191249.51822-1-abdul.rahim@myyahoo.com>
Le 13/09/2024 à 21:12, Abdul Rahim a écrit :
> strcpy() is generally considered unsafe and use of strscpy() is
> recommended [1]
>
> this fixes checkpatch warning:
> WARNING: Prefer strscpy over strcpy
>
> Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#strcpy [1]
> Signed-off-by: Abdul Rahim <abdul.rahim@myyahoo.com>
Hi,
in order to ease the review process, when you send a new version of a
patch, the subject line should state the version: (i.e.: [PATCH v2] ...)
It is also a good practice to explain what has changed with the previous
version.
Finally, it is nice to provide the link on lore to the previous version.
All this should added below the first ---.
Here it could look like:
> ---
Changes in v2:
- Remove an unneeded extra parameter (MAX_ACPI_DEVICE_NAME_LEN) in
the 2nd strscpy() call
v1:
https://lore.kernel.org/all/20240912205922.302036-1-abdul.rahim@myyahoo.com/
CJ
> drivers/acpi/thermal.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/acpi/thermal.c b/drivers/acpi/thermal.c
> index 78db38c7076e..6671537cb4b7 100644
> --- a/drivers/acpi/thermal.c
> +++ b/drivers/acpi/thermal.c
> @@ -796,9 +796,9 @@ static int acpi_thermal_add(struct acpi_device *device)
> return -ENOMEM;
>
> tz->device = device;
> - strcpy(tz->name, device->pnp.bus_id);
> - strcpy(acpi_device_name(device), ACPI_THERMAL_DEVICE_NAME);
> - strcpy(acpi_device_class(device), ACPI_THERMAL_CLASS);
> + strscpy(tz->name, device->pnp.bus_id);
> + strscpy(acpi_device_name(device), ACPI_THERMAL_DEVICE_NAME);
> + strscpy(acpi_device_class(device), ACPI_THERMAL_CLASS);
> device->driver_data = tz;
>
> acpi_thermal_aml_dependency_fix(tz);
next prev parent reply other threads:[~2024-09-13 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240913191249.51822-1-abdul.rahim.ref@myyahoo.com>
2024-09-13 19:12 ` Abdul Rahim
2024-09-13 19:31 ` Christophe JAILLET [this message]
2024-09-13 21:23 ` Abdul Rahim
[not found] <20240912205922.302036-1-abdul.rahim.ref@myyahoo.com>
2024-09-12 20:59 ` Abdul Rahim
2024-09-13 15:17 ` Christophe JAILLET
2024-09-13 18:13 ` Abdul Rahim
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=c4e7b3ac-d8fa-47b9-84f6-e3332bb54e12@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=abdul.rahim@myyahoo.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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
all inboxes | Powered by JetHome®