[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75a430de-54af-c4db-9d93-6b3d5e65874c@st.com>
Date: Wed, 29 Apr 2020 11:07:06 +0200
From: Christophe Kerello <christophe.kerello@...com>
To: Miquel Raynal <miquel.raynal@...tlin.com>,
Marek Vasut <marex@...x.de>
CC: <richard@....at>, <vigneshr@...com>, <lee.jones@...aro.org>,
<robh+dt@...nel.org>, <mark.rutland@....com>, <tony@...mide.com>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 04/12] mtd: rawnand: stm32_fmc2: manage all errors
cases at probe time
Hi Miquèl,
On 4/27/20 10:08 PM, Miquel Raynal wrote:
[...]
>>>> btw would it make sense to split the first three patches of this series
>>>> into a separate series ? This rawnand part seems more like an unrelated
>>>> cleanup.
>>> As it seems that the MFD discussion can take longer, then I would say
>>> yes, at least for the cleanup/misc changes part.
>> Right
>>
I think that it is better to only have one set of patches as there is
different maintainers that will review the whole set of patches.
I expect to be able to propose a v3 next week to add the EBI driver and
the updates on NAND driver (as some patches are linked)
A proposal could be to put all the NAND patches that you have started to
review at the beginning of the set of patches (patch 4/5/6/7/8).
You will be free to apply them after the review and I will only resubmit
the patches that have not been applied in the next version.
Regards,
Christophe Kerello.
Powered by blists - more mailing lists