From: Brian Norris <computersforpeace@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Zach Brown <zach.brown@ni.com>,
dwmw2@infradead.org, boris.brezillon@free-electrons.com,
dedekind1@gmail.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/5] mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Date: Wed, 8 Feb 2017 14:21:03 -0800 [thread overview]
Message-ID: <20170208222103.GI94627@google.com> (raw)
In-Reply-To: <20170208220345.GG94627@google.com>
On Wed, Feb 08, 2017 at 02:03:45PM -0800, Brian Norris wrote:
> I'm not sure what's happening with patches 3-5 yet either.
Never mind, those were reviewed and ready for me (not the NAND tree).
Applied 3 to 5 to l2-mtd.git.
next prev parent reply other threads:[~2017-02-08 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 19:30 [PATCH v8 0/5] mtd: use ONFI bad blocks per LUN to calculate UBI bad PEB limit Zach Brown
2017-01-10 19:30 ` [PATCH v8 1/5] mtd: introduce function max_bad_blocks Zach Brown
2017-01-10 19:30 ` [PATCH v8 2/5] mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available Zach Brown
2017-02-07 19:33 ` Richard Weinberger
2017-02-08 22:03 ` Brian Norris
2017-02-08 22:21 ` Brian Norris [this message]
2017-01-10 19:30 ` [PATCH v8 3/5] mtd: nand: Add max_bb_per_die and blocks_per_die fields to nand_chip Zach Brown
2017-01-10 19:30 ` [PATCH v8 4/5] mtd: nand: implement 'max_bad_blocks' mtd function Zach Brown
2017-01-10 19:30 ` [PATCH v8 5/5] mtd: nand: set max_bb_per_die and blocks_per_die for ONFI compliant chips Zach Brown
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=20170208222103.GI94627@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=zach.brown@ni.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.