[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o712qki7.fsf@bootlin.com>
Date: Mon, 23 Dec 2024 20:14:56 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: <broonie@...nel.org>
Cc: Md Sadre Alam <quic_mdalam@...cinc.com>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <andersson@...nel.org>,
<konradybcio@...nel.org>, <richard@....at>, <vigneshr@...com>,
<manivannan.sadhasivam@...aro.org>, <linux-arm-msm@...r.kernel.org>,
<linux-spi@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
<quic_srichara@...cinc.com>, <quic_varada@...cinc.com>
Subject: Re: [PATCH v14 0/8] Add QPIC SPI NAND driver
Hi Mark,
>> 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.
Do you want an immutable tag or will you wait the next cycle to apply
the spi patches?
Thanks,
Miquèl
> 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
Powered by blists - more mailing lists