From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: nand_bch: fix spelling of "probably"
Date: Fri, 6 May 2016 09:47:23 -0700 [thread overview]
Message-ID: <20160506164723.GA94236@google.com> (raw)
In-Reply-To: <20160506184444.69e7cc9b@bbrezillon>
On Fri, May 06, 2016 at 06:44:44PM +0200, Boris Brezillon wrote:
> On Fri, 6 May 2016 09:38:41 -0700
> Brian Norris <computersforpeace@gmail.com> wrote:
>
> > Signed-off-by: Brian Norris <computersforpeace@gmail.com>
>
> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> Can you take it directly into your tree before preparing your PR for
> Linus?
Done already :)
prev parent reply other threads:[~2016-05-06 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 16:38 [PATCH] mtd: nand_bch: fix spelling of "probably" Brian Norris
2016-05-06 16:42 ` Brian Norris
2016-05-06 16:44 ` Boris Brezillon
2016-05-06 16:47 ` 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=20160506164723.GA94236@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--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).