From: Sasha Levin <sashal@kernel.org>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>
Subject: Re: Patch "iio: light: isl29125: Use iio_push_to_buffers_with_ts() to allow source size runtime check" has been added to the 6.17-stable tree
Date: Wed, 5 Nov 2025 12:42:58 -0500 [thread overview]
Message-ID: <aQuMosXxq-F-_A_L@laps> (raw)
In-Reply-To: <20251105105311.000045bb@huawei.com>
On Wed, Nov 05, 2025 at 10:53:11AM +0000, Jonathan Cameron wrote:
>On Tue, 4 Nov 2025 18:36:44 -0500
>Sasha Levin <sashal@kernel.org> wrote:
>
>> This is a note to let you know that I've just added the patch titled
>>
>> iio: light: isl29125: Use iio_push_to_buffers_with_ts() to allow source size runtime check
>>
>> to the 6.17-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> iio-light-isl29125-use-iio_push_to_buffers_with_ts-t.patch
>> and it can be found in the queue-6.17 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>>
>
>This isn't a fix. Harmless if another fix needs it for context but
>in of itself not otherwise appropriate for stable.
>
>The hardening is against code bugs and there isn't one here - longer
>term we want to deprecate and remove the old interface.
Now dropped, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2025-11-05 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251104233644.350147-1-sashal@kernel.org>
2025-11-05 10:53 ` Patch "iio: light: isl29125: Use iio_push_to_buffers_with_ts() to allow source size runtime check" has been added to the 6.17-stable tree Jonathan Cameron
2025-11-05 17:42 ` Sasha Levin [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=aQuMosXxq-F-_A_L@laps \
--to=sashal@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=nuno.sa@analog.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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.