From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Tomas Borquez <tomasborquez13@gmail.com>,
andy@kernel.org, dlechner@baylibre.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
nuno.sa@analog.com
Subject: Re: [PATCH v3] iio: isl29018.c: replace sprintf with safer alternatives
Date: Sun, 7 Dec 2025 16:04:48 +0000 [thread overview]
Message-ID: <20251207160448.66c91da7@jic23-huawei> (raw)
In-Reply-To: <aSd3DT7XfcG5frc5@smile.fi.intel.com>
On Wed, 26 Nov 2025 23:54:21 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Wed, Nov 26, 2025 at 06:46:18PM -0300, Tomas Borquez wrote:
> > On Wed, Nov 26, 2025 at 11:09:07PM +0200, Andy Shevchenko wrote:
> > > This is a bit too long. Usually in the commit message the ~75 is a good
> > > threshold.
>
> ...
I tweaked the title as well to be:
iio: light: isl29018: replace sprintf() with safer alternatives
Applied to my currently local only togreg branch. I'll rebase on rc1 once it
is out and then it will turn up in linux-next etc.
>
> > > P.S. Do NOT resend if not asked so. Jonathan may amend this whilst applying.
> > > Also note, this most likely misses the v6.19-rc1, so we have plenty of time,
> > > no rush with it.
>
> > Ah I see, my bad, its my first patch so I'm still adjusting to the workflow.
> > Thanks for the feedback, will keep everything in mind!
>
> NP and welcome aboard!
>
Seconded!
prev parent reply other threads:[~2025-12-07 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 17:24 [PATCH v2] " Tomas Borquez
2025-11-26 19:35 ` Andy Shevchenko
2025-11-26 20:43 ` Tomas Borquez
2025-12-07 16:02 ` Jonathan Cameron
2025-11-26 20:32 ` [PATCH v3] " Tomas Borquez
2025-11-26 21:09 ` Andy Shevchenko
2025-11-26 21:46 ` Tomas Borquez
2025-11-26 21:54 ` Andy Shevchenko
2025-12-07 16:04 ` Jonathan Cameron [this message]
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=20251207160448.66c91da7@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=tomasborquez13@gmail.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®