From: Brian Norris <computersforpeace@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] MTD NAND fixes for v4.8-rc8
Date: Wed, 28 Sep 2016 12:31:34 -0700 [thread overview]
Message-ID: <20160928193134.GA142302@google.com> (raw)
In-Reply-To: <91984e2b-9bc9-0938-f4af-8decc00b7e63@nod.at>
Hi Richard,
On Fri, Sep 23, 2016 at 02:05:20PM +0200, Richard Weinberger wrote:
> This pull request contains fixes for bugs which got introduced in -rc1.
> You may wonder why I'm sending this pull request. Usually Brian takes NAND patches
> from Boris, but since Brian is very busy these days with other stuff and Boris is
> not yet member of the kernel.org web of trust I stepped in.
Thank you for doing this.
> Boris will be in Berlin at ELCE, I'll sign his key and hopefully other
> Kernel developers too such that he can issue his own pull requests soon.
Perfect.
> Brian, if there is anything wrong with this pull request, please let us know.
> We're not trying to bypass you. All we want is getting these fixes upstream
> before the merge window opens and new bugs emerge.
No problem, and all looks good. Sorry I've been too distracted :(
Unfortunately, there are also two other bugfixes I had queued in
linux-mtd.git weeks ago, and I didn't get around to sending a PR. They
are very minor (in risk and patch size) so I'll send the PR now.
Brian
prev parent reply other threads:[~2016-09-28 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 12:05 [GIT PULL] MTD NAND fixes for v4.8-rc8 Richard Weinberger
2016-09-28 19:31 ` Brian Norris [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=20160928193134.GA142302@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=torvalds@linux-foundation.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).