public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Huang Shijie <b32955@freescale.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/3] mtd: add new fields to nand_flash_dev{}
Date: Sat, 02 Mar 2013 16:19:32 +0200	[thread overview]
Message-ID: <1362233972.2745.7.camel@sauron> (raw)
In-Reply-To: <1359349039-11510-2-git-send-email-b32955@freescale.com>

On Mon, 2013-01-28 at 12:57 +0800, Huang Shijie wrote:
> As time goes on, we begin to meet the situation that we can not get enough
> information from some nand chips's id data. Take some Toshiba's nand chips
> for example. I have 4 Toshiba's nand chips in my hand:
> 	TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
> 
> When we read these chips' datasheets, we will get the geometry of these chips:
> 	TC58NVG2S0F : 4096 + 224
> 	TC58NVG3S0F : 4096 + 232
> 	TC58NVG5D2  : 8192 + 640
> 	TC58NVG6D2  : 8192 + 640
> 
> But we can not parse out the correct oob size for these chips from the id data.

Very good start of the commit message - you clearly defined the problem.

> So it is time to add some new fields to the nand_flash_dev{}, and update the
> detection mechanisms.

But continued with very poor description of how you address the problem.
Please, provide a better description.

> This patch just adds some new fields to the nand_flash_dev{}:
>   @id[8] : the 8 bytes id data.

id[8] = 8 bytes id data, just like password[5] = 5 bytes of password
data. Please, provide a better commentary.

>   @id_len: the valid length of the id data.

What does "valid" mean? Are "invalid" parts?

>   @oobsize: the oob size.

Try to invent a better comment.

Huang, it is not that I am trying to be difficult, but I truly do not
understand how you are solving the issue.

-- 
Best Regards,
Artem Bityutskiy


  parent reply	other threads:[~2013-03-02 14:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28  4:57 [PATCH V3 0/3] mtd: use the full-id as the keyword Huang Shijie
2013-01-28  4:57 ` [PATCH V3 1/3] mtd: add new fields to nand_flash_dev{} Huang Shijie
2013-02-12 15:47   ` Artem Bityutskiy
2013-02-16  3:56     ` Huang Shijie
2013-03-02 14:21       ` Artem Bityutskiy
2013-03-04  5:57         ` Huang Shijie
2013-03-04  7:50           ` Artem Bityutskiy
2013-03-04  8:08             ` Huang Shijie
2013-03-04  8:24               ` Artem Bityutskiy
2013-03-04  8:40                 ` Huang Shijie
2013-03-04  8:46                   ` Artem Bityutskiy
2013-03-04  8:59                     ` Huang Shijie
2013-03-04 19:27                       ` Brian Norris
2013-08-08 18:38                       ` Brian Norris
2013-03-04  8:37               ` Artem Bityutskiy
2013-03-04  8:57                 ` Huang Shijie
2013-02-28  8:25     ` Huang Shijie
2013-03-02 14:19   ` Artem Bityutskiy [this message]
2013-03-04  3:06     ` Huang Shijie
2013-01-28  4:57 ` [PATCH V3 2/3] mtd: add a new table for the unparsable nand chips Huang Shijie
2013-01-28  4:57 ` [PATCH V3 3/3] mtd: add the new detection method " Huang Shijie

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=1362233972.2745.7.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    /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