From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Kevin Cernekee <cernekee@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] mtd: nand: renumber conflicting BBT flags
Date: Mon, 04 Apr 2011 10:58:05 +0300 [thread overview]
Message-ID: <1301903885.2760.40.camel@localhost> (raw)
In-Reply-To: <1300510422-4841-1-git-send-email-computersforpeace@gmail.com>
On Fri, 2011-03-18 at 21:53 -0700, Brian Norris wrote:
> The NAND_USE_FLASH_BBT_NO_OOB and NAND_CREATE_EMPTY_BBT flags conflict
> with the NAND_BBT_SCANBYTE1AND6 and NAND_BBT_DYNAMICSTRUCT flags,
> respectively. This change will allow us to utilize these options
> independently.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
I've pushed both patches to l2-mtd-2.6.git, thanks.
P.S. Hopefully you won't be discouraged from doing further flags
polishing :-).
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-04 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 4:53 [PATCH 1/2] mtd: nand: renumber conflicting BBT flags Brian Norris
2011-03-19 4:53 ` [PATCH 2/2] mtd: nand: dynamic allocation of flash-based BBT structs Brian Norris
2011-03-31 12:58 ` [PATCH 1/2] mtd: nand: renumber conflicting BBT flags Artem Bityutskiy
2011-04-02 8:04 ` Brian Norris
2011-04-04 7:52 ` Artem Bityutskiy
2011-04-20 7:13 ` [RFC] mtd: nand: separate chip options / bbt_options Brian Norris
2011-04-22 8:02 ` Artem Bityutskiy
2011-05-25 18:15 ` Brian Norris
2011-05-26 8:04 ` Sebastian Andrzej Siewior
2011-05-31 17:25 ` Brian Norris
2011-04-04 7:58 ` Artem Bityutskiy [this message]
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=1301903885.2760.40.camel@localhost \
--to=dedekind1@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.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;
as well as URLs for NNTP newsgroup(s).