linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Schrempf Frieder <frieder.schrempf@kontron.de>
Cc: "vigneshr@ti.com" <vigneshr@ti.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] mtd: spinand: toshiba: Rename function name to change suffix and prefix (8Gbit)
Date: Thu, 5 Mar 2020 11:43:23 +0900	[thread overview]
Message-ID: <f6501db6-8dcd-ec13-de6a-b782656de0e7@kioxia.com> (raw)
In-Reply-To: <20200302101254.31ca0c83@xps13>


On 2020/03/02 18:12, Miquel Raynal wrote:
> Hello,
>
> Schrempf Frieder <frieder.schrempf@kontron.de> wrote on Mon, 2 Mar 2020
> 08:02:25 +0000:
>
>> On 28.02.20 04:11, Yoshio Furuyama wrote:
>>> The suffix was changed to classify from "g" to "j" between 1st generation
>>> device and 2nd generation device that's new Serial NAND of Kioxia brand.
>> I had to read this sentence multiple times to understand it. Maybe
>> something like this would be better:
>>
>>     The suffix was changed from "g" to "j" to classify between 1st
>>     generation and 2nd generation serial NAND devices (which now belong to
>>     the Kioxia brand).
Thanks comment,     I will send revise rev.
>>> As reference that's
>>> 1st generation device of 1Gbit product is "tc58cvg0s3hraig"
>>> 2nd generation device of 1Gbit product is "tc58cvg0s3hraij".
>>>
>>> The 8Gbit product "TH58CxG3S0HRAIJ" is new line up of Kioxia's serial nand
>>> and changed the prefix from tc58 to th58.
>>> Thus it was changed argument to the function from "tc58cxgxsx" to
>>> "tx58cxgxsxraix".
>> Same here. It is very hard to read. I would write something like this:
>>
>>     The 8Gbit type "TH58CxG3S0HRAIJ" is new to Kioxia's serial NAND lineup
>>     and the prefix was changed from "TC58" to "TH85".
>>
>>     Thus the functions were renamed from tc58cxgxsx_*() to
>>     tx58cxgxsxraix_*().

I will change prefix from "TH85" to "TH58" .  Since this is typo.

    The 8Gbit type "TH58CxG3S0HRAIJ" is new to Kioxia's serial NAND lineup
    and the prefix was changed from "TC58" to "TH58".

    Thus the functions were renamed from tc58cxgxsx_*() to
    tx58cxgxsxraix_*().

Thanks,

>> With an easier to understand commit message:
>>
>> Reviewed-by: Frieder Schrempf <frieder.schrempf@kontron.de>
> Agreed, the commit log proposal from Frieder looks better.
>
> The rest of the patch is fine by me though.
>
> Thanks,
> Miquèl
>
>

  reply	other threads:[~2020-03-05  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  3:11 [PATCH v2 0/2] mtd: spinand: toshiba: Support for new Kioxia Serial NAND Yoshio Furuyama
2020-02-28  3:11 ` [PATCH v2 1/2] mtd: spinand: toshiba: Rename function name to change suffix and prefix (8Gbit) Yoshio Furuyama
2020-03-02  8:02   ` Schrempf Frieder
2020-03-02  9:12     ` Miquel Raynal
2020-03-05  2:43       ` Yoshio Furuyama [this message]
2020-02-28  3:12 ` [PATCH v2 2/2] mtd: spinand: toshiba: Support for new Kioxia Serial NAND Yoshio Furuyama
2020-03-02  8:03   ` Schrempf Frieder

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=f6501db6-8dcd-ec13-de6a-b782656de0e7@kioxia.com \
    --to=ytc-mb-yfuruyama7@kioxia.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --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).