From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>
Cc: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
bbrezillon@kernel.org, linux-mtd@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_srichara@quicinc.com, quic_varada@quicinc.com,
quic_nainmeht@quicinc.com, quic_laksd@quicinc.com
Subject: Re: [PATCH v2 0/3] QPIC v2 fixes for SDX75
Date: Mon, 6 Jan 2025 19:34:17 +0530 [thread overview]
Message-ID: <20250106140417.ypyynt2xvixiixhb@thinkpad> (raw)
In-Reply-To: <18af7a68-42a3-6a82-c1b1-38ba8b06ed78@quicinc.com>
On Tue, Dec 24, 2024 at 10:52:03AM +0530, Md Sadre Alam wrote:
>
>
> On 12/20/2024 3:00 PM, Manivannan Sadhasivam wrote:
> > On Fri, Nov 22, 2024 at 02:29:30PM +0530, Md Sadre Alam wrote:
> > > v2:
> > > * Updated commit message
> > > * Added stable kernel tag
> > > * Added Fixes tag
> > > * Renamed the variable from offset_from_qpic to nandc_offset
> > > * Set buf_count to 512 in the parameter page read
> > > * Replaced the buf_count value of 512 with the len in bytes
> > >
> > > v1:
> > > * These patches will fix the following:
> > > * 1) onfi param page read which was broken by exec_op() patch.
> > > * 2) Fixed offset passed to BAM from QPIC base
> > >
> > > Md Sadre Alam (3):
> > > mtd: rawnand: qcom: Pass 18 bit offset from QPIC base address to BAM
> > > mtd: rawnand: qcom: Fix onfi param page read
> > > mtd: rawnand: qcom: Fix read len for onfi param page
> > >
> >
> > Do you plan to respin this series? FYI, these are regressions, so should go in
> > early as possible.
> Waiting for SPI NAND series patches [1] to be merged (raw nand change patch
> 2-5). On top of that will repost these patches.
This series fixes regression, so these should be merged first. Do not make fixes
depend on feature.
- Mani
--
மணிவண்ணன் சதாசிவம்
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2025-01-06 14:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 8:59 [PATCH v2 0/3] QPIC v2 fixes for SDX75 Md Sadre Alam
2024-11-22 8:59 ` [PATCH v2 1/3] mtd: rawnand: qcom: Pass 18 bit offset from QPIC base address to BAM Md Sadre Alam
2024-11-26 5:30 ` Manivannan Sadhasivam
2024-11-27 9:05 ` Md Sadre Alam
2024-11-22 8:59 ` [PATCH v2 2/3] mtd: rawnand: qcom: Fix onfi param page read Md Sadre Alam
2024-11-26 5:41 ` Manivannan Sadhasivam
2024-11-27 9:11 ` Md Sadre Alam
2024-11-22 8:59 ` [PATCH v2 3/3] mtd: rawnand: qcom: Fix read len for onfi param page Md Sadre Alam
2024-11-26 5:45 ` Manivannan Sadhasivam
2024-11-26 5:49 ` Manivannan Sadhasivam
2024-11-22 17:44 ` [PATCH v2 0/3] QPIC v2 fixes for SDX75 Lakshmi Sowjanya D (QUIC)
2024-12-20 9:30 ` Manivannan Sadhasivam
2024-12-24 5:22 ` Md Sadre Alam
2024-12-24 8:09 ` Miquel Raynal
2024-12-24 11:53 ` Md Sadre Alam
2025-01-06 14:04 ` Manivannan Sadhasivam [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=20250106140417.ypyynt2xvixiixhb@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bbrezillon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=quic_laksd@quicinc.com \
--cc=quic_mdalam@quicinc.com \
--cc=quic_nainmeht@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