From: Zach Brown <zach.brown@ni.com>
To: "Honza Petrouš" <jpetrous@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
dedekind1@gmail.com, linux-kernel@vger.kernel.org,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org, cyrille.pitchen@atmel.com,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [RESEND PATCH v3] UBI: add debugfs file for tracking PEB state
Date: Wed, 17 May 2017 12:55:47 -0500 [thread overview]
Message-ID: <20170517175546.GA7493@zach-desktop> (raw)
In-Reply-To: <CAJbz7-2D4ZVyWcC+bx5aFMS7FjRWX-_AWyKODt4civz4fJverg@mail.gmail.com>
On Wed, May 17, 2017 at 12:36:35PM +0200, Honza Petrouš wrote:
> 2017-05-16 20:22 GMT+02:00 Richard Weinberger <richard@nod.at>:
> > Zach,
> >
> > Am 16.05.2017 um 19:58 schrieb Zach Brown:
> >> From: Ben Shelton <ben.shelton@ni.com>
> >>
> >> Add a file under debugfs to allow easy access to the erase count for
> >> each physical erase block on an UBI device. This is useful when
> >> debugging data integrity issues with UBIFS on NAND flash devices.
> >>
> >> Signed-off-by: Ben Shelton <ben.shelton@ni.com>
> >> Signed-off-by: Zach Brown <zach.brown@ni.com>
> >
> > Hmmm, I thought I applied this to my v4.12 queue, but seems
> > like I didn't. So, it will be part of v4.13.
> > I'm very sorry, please accept my apologies.
>
> Yes, you did it - at least my Linus' github repo clone has it already
> = 7bccd12d27b7e358823feb5429731b8ee698b173
>
> /Honza
My mistake then. My apologies for the confusion. Thank you for noticing.
prev parent reply other threads:[~2017-05-17 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:58 [RESEND PATCH v3] UBI: add debugfs file for tracking PEB state Zach Brown
2017-05-16 18:22 ` Richard Weinberger
2017-05-17 10:36 ` Honza Petrouš
2017-05-17 17:55 ` Zach Brown [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=20170517175546.GA7493@zach-desktop \
--to=zach.brown@ni.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jpetrous@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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