X86 platform drivers
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <markgross@kernel.org>,
	Maximilian Luz <luzmaximilian@gmail.com>,
	Divya Bharathi <divya.bharathi@dell.com>,
	Prasanth Ksr <prasanth.ksr@dell.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Dell.Client.Kernel@dell.com,
	Thinkpad-acpi devel ML <ibm-acpi-devel@lists.sourceforge.net>
Subject: Re: [PATCH] platform: move from strlcpy with unused retval to strscpy
Date: Fri, 19 Aug 2022 11:19:01 +0200	[thread overview]
Message-ID: <Yv9VhdVXqXhONj41@shikoro> (raw)
In-Reply-To: <CAHp75VeM2q7wdnREoenyYpJ-tso2G6M-uyGFJGjPGL8hfUmzhQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]


> I assume you are experimenting with coccinelle, so I have no objection
> to the change, but in PDx86 we usually want to have one patch per
> driver. Can you split?

I can split if you want.

I intentionally did group per subsystem, otherwise I would have sent out
1200+ patches. So, I chose to do it on subsystem level first and adapt
later where this scheme does not fit.

So, your choice.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-08-19  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 21:00 [PATCH] platform: move from strlcpy with unused retval to strscpy Wolfram Sang
2022-08-18 21:58 ` Maximilian Luz
2022-08-19  6:22 ` Andy Shevchenko
2022-08-19  8:57   ` Hans de Goede
2022-08-19  9:19   ` Wolfram Sang [this message]
2022-08-19  9:20     ` Hans de Goede
2022-08-26 10:01 ` Hans de Goede

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=Yv9VhdVXqXhONj41@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=divya.bharathi@dell.com \
    --cc=hdegoede@redhat.com \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=prasanth.ksr@dell.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