From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Leo Li <pku.leo@gmail.com>, Yang-Leo Li <leoyang.li@nxp.com>,
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>,
Scott Wood <oss@buserror.net>,
Raghav Dogra <raghav.dogra@nxp.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Raghav Dogra <raghav@freescale.com>,
Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [PATCH][v3] mtd/ifc: Add support for IFC controller version 2.0
Date: Fri, 27 May 2016 23:16:05 +0200 [thread overview]
Message-ID: <20160527231605.3b06b67c@bbrezillon> (raw)
In-Reply-To: <20160527211247.GA123214@google.com>
On Fri, 27 May 2016 14:12:47 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
>
> > Anyway, Brian, can you take it into your tree and make it appear in
> > -rc1 (or earlier if it's still possible)?
>
> Not sure how I could get it any "earlier"? It's not making -rc1 at this
> point.
I meant -rc2 :)
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-27 21:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 11:24 [PATCH][v3] mtd/ifc: Add support for IFC controller version 2.0 Raghav Dogra
2016-02-17 21:49 ` Scott Wood
2016-02-18 21:18 ` Leo Li
2016-02-19 0:07 ` Scott Wood
2016-03-30 20:43 ` Li Yang
2016-04-06 17:52 ` Brian Norris
2016-04-06 18:53 ` Yang-Leo Li
2016-04-08 0:45 ` Boris Brezillon
2016-05-25 19:18 ` Leo Li
2016-05-25 20:34 ` Boris Brezillon
2016-05-27 20:15 ` Leo Li
2016-05-27 20:44 ` Boris Brezillon
2016-05-27 21:12 ` Brian Norris
2016-05-27 21:16 ` Boris Brezillon [this message]
2016-05-27 22:03 ` Leo Li
2016-06-29 14:53 ` Raghav Dogra
2016-06-29 17:32 ` Brian Norris
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=20160527231605.3b06b67c@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=b44839@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=leoyang.li@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=pku.leo@gmail.com \
--cc=prabhakar.kushwaha@nxp.com \
--cc=raghav.dogra@nxp.com \
--cc=raghav@freescale.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 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).