From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Jeff Kletsky <lede@allycomm.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spinand: Add support for GigaDevice GD5F1GQ4UFxxG
Date: Tue, 14 May 2019 16:11:28 +0000 [thread overview]
Message-ID: <e53a0569-6eca-4385-007d-baffc3f5c7ea@kontron.de> (raw)
In-Reply-To: <1023ba21-b188-1dcc-3ecc-c563d4cb8a67@allycomm.com>
Hi Jeff,
On 14.05.19 17:42, Jeff Kletsky wrote:
> On 5/13/19 6:56 AM, Schrempf Frieder wrote:
>
>> Hi Jeff,
>>
>> I just noticed I hit the wrong button and my previous reply was only
>> sent to the MTD list, so I'm resending with fixed recipients...
>>
>> On 10.05.19 14:17,lede@allycomm.com wrote:
>>> From: Jeff Kletsky<git-commits@allycomm.com>
>>>
>>> The GigaDevice GD5F1GQ4UFxxG SPI NAND is in current production devices
>>> and, while it has the same logical layout as the E-series devices,
>>> it differs in the SPI interfacing in significant ways.
>>>
>>> To accommodate these changes, this patch also:
>>>
>>> * Adds support for two-byte manufacturer IDs
>>> * Adds #define-s for three-byte addressing for read ops
>>>
>>> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>>>
>>> Signed-off-by: Jeff Kletsky<git-commits@allycomm.com>
>> Maybe it would be better to split this patch into three parts:
>> * Add support for two-byte device IDs
>> * Add #define-s for three-byte addressing for read ops
>> * Add support for GD5F1GQ4UFxxG
>>
>> Anyway the content looks good to me, so:
>>
>> Reviewed-by: Frieder Schrempf<frieder.schrempf@kontron.de>
>>
>> [...]
>
> Thanks for the time in review and good words!
You're welcome!
> My apologies for an incomplete git-send-email config that left
> me nameless in the headers.
No problem, I guessed your name from the Signed-off-by tag ;)
> I wasn't sure if that was direction to submit as three patches
> at this time, but would be happy to do so if the consensus is
> that it the direction to follow.
I think it's common to separate logical different changes. This makes it
easier to read.
Also the preparation changes only touch the SPI NAND core. I guess
that's another reason why they should be separated from the
chip-specific changes.
> At least for me, I feel that the other two don't really stand
> on their own without the context for their need.
I don't think that's a problem. Just add a note to the commit message
that these core changes are needed to prepare for the GD5F1GQ4UFxxG support.
Thanks,
Frieder
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-05-14 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 12:17 [PATCH] mtd: spinand: Add support for GigaDevice GD5F1GQ4UFxxG lede
2019-05-13 7:02 ` Schrempf Frieder
2019-05-13 13:56 ` Schrempf Frieder
[not found] ` <1023ba21-b188-1dcc-3ecc-c563d4cb8a67@allycomm.com>
2019-05-14 16:11 ` Schrempf Frieder [this message]
2019-05-14 20:01 ` Miquel Raynal
2019-05-14 22:08 ` Jeff Kletsky
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=e53a0569-6eca-4385-007d-baffc3f5c7ea@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=lede@allycomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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