From: Scott Wood <scottwood@freescale.com>
To: Huang Shijie <shijie8@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
dedekind1@gmail.com, Jan Weitzel <j.weitzel@phytec.de>,
Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH] mtd: add a new macro about the subpage write
Date: Fri, 13 Jul 2012 11:29:58 -0500 [thread overview]
Message-ID: <50004D06.10303@freescale.com> (raw)
In-Reply-To: <CAMiH66FNn3YrqiCdYj7aAP8qR3VtH5r7q4Gza=0=vQtOoj_5bw@mail.gmail.com>
On 07/13/2012 11:08 AM, Huang Shijie wrote:
> On Fri, Jul 13, 2012 at 11:40 AM, Marek Vasut <marex@denx.de> wrote:
>> Dear Huang Shijie,
>>
>>> On Fri, Jul 13, 2012 at 6:35 AM, Marek Vasut <marex@denx.de> wrote:
>>>> Dear Huang Shijie,
>>>>
>>>>> Hi Brian:
>>>>>> Wood [1]; I don't see a good reason not to just kill the
>>>>>> NAND_CHIPOPTIONS_MSK instead of adding more flags. As long as we
>>>>>> perform a few sanity tests, I think it'd be safe.
>>>>>
>>>>> I think it's more clear in logic to add this new macro:
>>>>> The NAND_NO_SUBPAGE_WRITE can be used only by the MLC nands which do
>>>>>
>>>>> no support the subpage write;
>>>>>
>>>>> The NAND_CONTROLLER_NO_SUBPAGE_WRITE only used by the nand
>>>>>
>>>>> controller such as gpmi nand.
>>>>
>>>> It's not clearer at all. It's just more error-prone.
>>>
>>> ok, thanks. But I do not how to fix it now. I hope some one could give a
>>> patch.
>>
>> Why not remove the mask?
>>
>
> I do not understand why this line was added here, was it added on purpose?
> so I am not sure whether we can just remove this line.
If whoever wanted that line to be there cared enough, they could have
justified it with a comment (in the code, in the changelog, or in one of
these threads). We can't just let cruft sit there (or worse, produce
more cruft to work around existing cruft) just because we don't know
exactly what the original author was thinking. It appears to just have
been a misguided attempt at enforcing any given option to come from only
one place.
-Scott
next prev parent reply other threads:[~2012-07-13 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 5:32 [PATCH] mtd: add a new macro about the subpage write Huang Shijie
2012-07-11 6:07 ` Brian Norris
2012-07-11 7:13 ` Huang Shijie
2012-07-13 10:35 ` Marek Vasut
2012-07-13 14:00 ` Huang Shijie
2012-07-13 15:40 ` Marek Vasut
2012-07-13 16:08 ` Huang Shijie
2012-07-13 16:28 ` Marek Vasut
2012-07-13 16:29 ` Scott Wood [this message]
2012-07-13 16:53 ` Marek Vasut
2012-07-13 17:02 ` Brian Norris
2012-07-13 17:10 ` Marek Vasut
2012-07-13 17:35 ` [PATCH] mtd: add a new macro about the subpage write (REPORT SPAM) William F.
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=50004D06.10303@freescale.com \
--to=scottwood@freescale.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=j.weitzel@phytec.de \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=shijie8@gmail.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