From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Josh Law <objecting@objecting.org>
Cc: Kees Cook <kees@kernel.org>,
"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>,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v1 1/1] ACPI: processor: idle: Replace strlcat() with better alternative
Date: Fri, 20 Mar 2026 21:39:10 +0200 [thread overview]
Message-ID: <ab2iXmvgJID3bAmg@ashevche-desk.local> (raw)
In-Reply-To: <308B1431-EEA5-4114-9587-A553CCE75A22@objecting.org>
On Fri, Mar 20, 2026 at 07:31:54PM +0000, Josh Law wrote:
>
>
> >Thank you for confirming, this is basically the message to Josh to find
> >users and start converting them and kill strlcat() eventually. Josh, as
> >you see it will be well appreciated!
>
> Thank you! But the only reason I'm not doing it is because if I submit all of
> the patches, let's say, 50 gets merged (including strings.c) and like 50
> don't, then 50 will have a nonexistent/slow API because they chose to not
> merge my patch
Huh?! Even if you do 50%, it will still be appreciated as it's not a job that
has to be done in one cycle. Also we expect to have a constructive feedback
from the maintainers. Killing an old and confusing API is a good justification
and it will be rare maintainer even thinking to tell against. The feedback
may be given to the implementation and how to improve or adjust, but believe
close to 0 maintainers will say a word against dropping strlcat().
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-20 19:39 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
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 [this message]
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=ab2iXmvgJID3bAmg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.