From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Md Sadre Alam <quic_mdalam@quicinc.com>
Cc: <broonie@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <andersson@kernel.org>,
<konradybcio@kernel.org>, <richard@nod.at>, <vigneshr@ti.com>,
<manivannan.sadhasivam@linaro.org>,
<linux-arm-msm@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <quic_srichara@quicinc.com>,
<quic_varada@quicinc.com>
Subject: Re: [PATCH v14 0/8] Add QPIC SPI NAND driver
Date: Mon, 02 Dec 2024 17:57:09 +0100 [thread overview]
Message-ID: <87mshe58gq.fsf@bootlin.com> (raw)
In-Reply-To: <20241120091507.1404368-1-quic_mdalam@quicinc.com> (Md Sadre Alam's message of "Wed, 20 Nov 2024 14:44:58 +0530")
Hi Marc,
On 20/11/2024 at 14:44:58 +0530, Md Sadre Alam <quic_mdalam@quicinc.com> wrote:
> v14:
> * Updated commit message
> * Fix spelling mistake
> * Remove "inline" from multiple APIs from qcom_nandc.c file
> * Move '|' in qcom_param_page_type_exec() APIs at the end of line
I guess it is now time to move on, I can apply patches 2-5 and share an
immutable tag. However, due to the frequent inconsistencies observed
during the lifetime of this patchset, we might be slightly more
conservative than usual and split the patches over two kernel
releases. I fear there might be annoying fixes on the mtd side needed
because of some side effects. Without these, the spi tree might have
broken qcom support for several weeks. What do you think?
Cheers,
Miquèl
next prev parent reply other threads:[~2024-12-02 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 9:14 [PATCH v14 0/8] Add QPIC SPI NAND driver Md Sadre Alam
2024-11-20 9:14 ` [PATCH v14 1/8] spi: dt-bindings: Introduce qcom,spi-qpic-snand Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 2/8] mtd: rawnand: qcom: cleanup qcom_nandc driver Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 3/8] mtd: rawnand: qcom: Add qcom prefix to common api Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 4/8] mtd: nand: Add qpic_common API file Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 5/8] mtd: rawnand: qcom: use FIELD_PREP and GENMASK Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 6/8] spi: spi-qpic: add driver for QCOM SPI NAND flash Interface Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 7/8] arm64: dts: qcom: ipq9574: Add SPI nand support Md Sadre Alam
2024-12-05 17:19 ` Konrad Dybcio
2024-12-09 5:32 ` Md Sadre Alam
2024-11-20 9:15 ` [PATCH v14 8/8] arm64: dts: qcom: ipq9574: Remove eMMC node Md Sadre Alam
2024-12-05 17:19 ` Konrad Dybcio
2024-12-02 16:57 ` Miquel Raynal [this message]
2024-12-03 11:04 ` [PATCH v14 0/8] Add QPIC SPI NAND driver Md Sadre Alam
2024-12-23 19:14 ` Miquel Raynal
2024-12-24 5:07 ` Md Sadre Alam
2024-12-24 15:43 ` 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=87mshe58gq.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.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=manivannan.sadhasivam@linaro.org \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--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).