From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Josh Law <objecting@objecting.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
kees@kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v1 1/1] ACPI: processor: idle: Replace strlcat() with better alternative
Date: Mon, 16 Mar 2026 21:42:49 +0200 [thread overview]
Message-ID: <abhdOes2GSRZdWh3@ashevche-desk.local> (raw)
In-Reply-To: <590CA4EE-3510-482D-B768-91B3CFC73164@objecting.org>
On Mon, Mar 16, 2026 at 06:49:23PM +0000, Josh Law wrote:
> On 16 March 2026 18:47:45 GMT, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >On Mon, Mar 16, 2026 at 06:43:58PM +0000, Josh Law wrote:
> >> On 16 March 2026 17:01:58 GMT, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >> >strlcpy() and strlcat() are confusing APIs and the former one already gone
> >> >from the kernel. In preparation to kill strlcat() replace it with the better
> >> >alternative.
> >>
> >> Is this patch in relation to my string.c patch?
> >
> >Yes.
> >
> >> You would have to do this for about 120~ files.
> >
> >Not me, just showing you what to do.
> >
> >Btw, what kind of assistance do you use for the patches?
>
> None
Hmm... Many patches that are generated require quite a lot of time investment
and understanding the code. It's unbelievable that a person can do that without
an assistance.
> I use grep to find all the files calling the functions (took a while!)
No, that's not what I was asking about.
> And if I did those patches, I can't guarantee all of them will be ACKed.
Interesting way of saying the obvious. And if you didn't?..
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-16 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 17:01 [PATCH v1 1/1] ACPI: processor: idle: Replace strlcat() with better alternative Andy Shevchenko
2026-03-16 18:43 ` Josh Law
2026-03-16 18:47 ` Andy Shevchenko
2026-03-16 18:49 ` Josh Law
2026-03-16 19:42 ` Andy Shevchenko [this message]
2026-03-16 19:51 ` Josh Law
2026-03-17 8:17 ` kernel test robot
2026-03-17 8:29 ` Andy Shevchenko
2026-03-20 19:17 ` Kees Cook
2026-03-20 19:25 ` Andy Shevchenko
2026-03-20 19:26 ` Kees Cook
2026-03-20 19:31 ` Josh Law
2026-03-20 19:39 ` Andy Shevchenko
2026-03-20 19:34 ` Kees Cook
2026-03-20 19:39 ` 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=abhdOes2GSRZdWh3@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=kees@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=objecting@objecting.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@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