From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: andersson@kernel.org, konrad.dybcio@linaro.org,
broonie@kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
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 0/5] Add QPIC SPI NAND driver
Date: Tue, 20 Feb 2024 12:36:18 +0100 [thread overview]
Message-ID: <454a7e8d-70f5-4bf5-a3f1-bf9e42672c4c@linaro.org> (raw)
In-Reply-To: <3ad2909d-4ac3-fff3-739d-b12a3408fa0f@quicinc.com>
On 20/02/2024 12:32, Md Sadre Alam wrote:
>
>
> On 2/19/2024 6:34 PM, Manivannan Sadhasivam wrote:
>> On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote:
>>> This series of patches will add initial supports
>>> for QPIC SPI NAND driver.
>>>
>>> Currently this driver support following commands
>>>
>>> -- RESET
>>> -- READ ID
>>> -- BLOCK ERASE
>>> -- PAGE READ
>>> -- PAGE WRITE
>>> -- GET FEATURE
>>> -- SET FEATURE
>>> -- BAD BLOCK CHECK
>>>
>>> This driver has been tested with dd command with read/write page
>>> with multiple file size 1MiB, 10MiB,40MiB etc.
>>> Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc.
>>>
>>
>> This is not the first version isn't it? Where is the changelog describing what
>> has changed since then?
>
> The earlier patch was the RFC for design review only.
RFC is state of patch, not version. This is v2 then.
These RFC postings are really becoming mess. Some people make multiple
RFCs and then post v1 hiding entire previous history... And why even
bother with calling it RFC?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-20 11:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 13:48 [PATCH 0/5] Add QPIC SPI NAND driver Md Sadre Alam
2024-02-15 13:48 ` [PATCH 1/5] spi: dt-bindings: add binding doc for spi-qpic-snand Md Sadre Alam
2024-02-15 14:22 ` Mark Brown
2024-02-20 12:05 ` Md Sadre Alam
2024-02-15 14:24 ` Conor Dooley
2024-02-20 12:06 ` Md Sadre Alam
2024-02-15 19:02 ` Krzysztof Kozlowski
2024-02-20 12:28 ` Md Sadre Alam
2024-02-15 13:48 ` [PATCH 2/5] drivers: mtd: nand: Add qpic_common API file Md Sadre Alam
2024-02-15 15:00 ` Dmitry Baryshkov
2024-02-20 15:59 ` Md Sadre Alam
2024-02-20 16:07 ` Dmitry Baryshkov
2024-02-21 10:38 ` Md Sadre Alam
2024-02-15 17:55 ` Konrad Dybcio
2024-02-20 12:21 ` Md Sadre Alam
2024-02-16 15:29 ` Kathiravan Thirumoorthy
2024-02-20 12:30 ` Md Sadre Alam
2024-02-15 13:48 ` [PATCH 3/5] spi: spi-qpic: Add qpic spi nand driver support Md Sadre Alam
2024-02-15 14:14 ` Mark Brown
2024-02-20 11:54 ` Md Sadre Alam
2024-02-20 16:04 ` Mark Brown
2024-02-21 10:36 ` Md Sadre Alam
2024-02-15 17:57 ` Konrad Dybcio
2024-02-20 12:14 ` Md Sadre Alam
2024-03-06 6:01 ` Md Sadre Alam
2024-03-06 16:27 ` Konrad Dybcio
2024-03-07 4:10 ` Md Sadre Alam
2024-02-17 13:48 ` kernel test robot
2024-02-17 18:41 ` kernel test robot
2024-02-18 8:14 ` kernel test robot
2024-02-15 13:48 ` [PATCH 4/5] arm64: dts: qcom: ipq9574: Add SPI nand support Md Sadre Alam
2024-02-16 15:40 ` Kathiravan Thirumoorthy
2024-02-20 12:31 ` Md Sadre Alam
2024-02-15 13:48 ` [PATCH 5/5] arm64: dts: qcom: ipq9574: Disable eMMC node Md Sadre Alam
2024-02-15 15:00 ` Dmitry Baryshkov
2024-02-15 17:58 ` Konrad Dybcio
2024-02-20 12:16 ` Md Sadre Alam
2024-02-20 12:12 ` Md Sadre Alam
2024-02-16 15:43 ` Kathiravan Thirumoorthy
2024-02-20 12:33 ` Md Sadre Alam
2024-02-19 13:04 ` [PATCH 0/5] Add QPIC SPI NAND driver Manivannan Sadhasivam
2024-02-20 11:32 ` Md Sadre Alam
2024-02-20 11:36 ` Krzysztof Kozlowski [this message]
2024-02-21 10:34 ` Md Sadre Alam
2024-02-21 11:01 ` Krzysztof Kozlowski
2024-02-21 11:08 ` Md Sadre Alam
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=454a7e8d-70f5-4bf5-a3f1-bf9e42672c4c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@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=manivannan.sadhasivam@linaro.org \
--cc=miquel.raynal@bootlin.com \
--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).