From: Jerome Brunet <jbrunet@baylibre.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 6.12.y] clk: meson: align gxbb_32k_clk_sel number of parents with actual count
Date: Fri, 11 Sep 2026 21:05:34 +0200 [thread overview]
Message-ID: <1jfqzf7gn5.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <aqRAbyxpEnKlOXOu@laps>
On ven. 11 sept. 2026 at 13:54, Sasha Levin <sashal@kernel.org> wrote:
> On Fri, Sep 11, 2026 at 03:07:54PM +0200, Jerome Brunet wrote:
>>On ven. 11 sept. 2026 at 07:20, Sasha Levin <sashal@kernel.org> wrote:
>>
>>>> The following out-of-bounds read has been observed by Christian on a
>>>> GXBB WeTek Hub:
>>>
>>> Queued for 6.12, thanks.
>>
>>Hello Sasha,
>>
>>In those instance where exact same backport applies to multiple versions
>>how do you prefer to handle things ?
>>
>>* Just replying 5 times as I did ?
>>* Just reply once with a note explaining that it applies to other version ?
>
> Hey!
>
> Either works - so whatever is easier for you.
>
> Something along the lines of "[PATCH 6.18-6.1]" is what most folks use.
Noted. Thanks a lot
>
> --
> Thanks,
> Sasha
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
--
Jerome
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2026-09-11 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026090928-nylon-handoff-edb8@gregkh>
2026-09-10 7:21 ` Jerome Brunet
2026-09-11 11:20 ` Sasha Levin
2026-09-11 13:07 ` Jerome Brunet
2026-09-11 17:54 ` Sasha Levin
2026-09-11 19:05 ` Jerome Brunet [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=1jfqzf7gn5.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=sashal@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 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®