From: Gabor Juhos <j4g8y7@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mark Brown <broonie@kernel.org>,
Md Sadre Alam <quic_mdalam@quicinc.com>,
Varadarajan Narayanan <quic_varada@quicinc.com>,
Sricharan Ramabadhran <quic_srichara@quicinc.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-spi@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Lakshmi Sowjanya D <quic_laksd@quicinc.com>
Subject: Re: [PATCH v2 2/2] mtd: nand: qpic_common: prevent out of bounds access of BAM arrays
Date: Tue, 3 Jun 2025 11:16:49 +0200 [thread overview]
Message-ID: <08ef60a0-b78c-47a8-abb7-2de08303ae4d@gmail.com> (raw)
In-Reply-To: <87a56qp7um.fsf@bootlin.com>
2025. 06. 02. 15:54 keltezéssel, Miquel Raynal írta:
>
> On 30/05/2025 at 13:07:35 +02, Gabor Juhos <j4g8y7@gmail.com> wrote:
>
>> 2025. 05. 30. 10:56 keltezéssel, Bryan O'Donoghue írta:
>>
>> ...
>>
>>> This one doesn't apply to -next
>>
>> It is because the series is based on the SPI tree, and -next contains another
>> change for 'drivers/mtd/nand/qpic_common.c' which comes from the MTD tree.
>>
>> It can be applied by specifying the 'M' switch for b4 shazam.
>
> I suggest you rebase on -rc1 (when it's out) and resend to simplify
> Mark's life.
I will do that, thanks!
Regards,
Gabor
next prev parent reply other threads:[~2025-06-03 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 17:25 [PATCH v2 0/2] spi: spi-qpic-snand: avoid memory corruption Gabor Juhos
2025-05-29 17:25 ` [PATCH v2 1/2] spi: spi-qpic-snand: reallocate BAM transactions Gabor Juhos
2025-05-29 17:25 ` [PATCH v2 2/2] mtd: nand: qpic_common: prevent out of bounds access of BAM arrays Gabor Juhos
2025-05-30 8:56 ` Bryan O'Donoghue
2025-05-30 11:07 ` Gabor Juhos
2025-06-02 13:54 ` Miquel Raynal
2025-06-03 9:16 ` Gabor Juhos [this message]
2025-06-02 13:53 ` Miquel Raynal
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=08ef60a0-b78c-47a8-abb7-2de08303ae4d@gmail.com \
--to=j4g8y7@gmail.com \
--cc=broonie@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=quic_laksd@quicinc.com \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).