From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: request bitrev patch merge
Date: Mon, 15 Dec 2014 10:25:54 +0000 [thread overview]
Message-ID: <20141215102554.GC11285@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20141215095239.GB11285@n2100.arm.linux.org.uk>
On Mon, Dec 15, 2014 at 09:52:39AM +0000, Russell King - ARM Linux wrote:
> On Mon, Dec 15, 2014 at 02:02:50PM +0800, Wang, Yalin wrote:
> > Hi
> >
> > Joe's patch that remove use byte_rev_table directly have
> > Been merged into linux-next branch ,
> > Cou you merge 8187/1 8205/1 8189/1 patch for arm ?
>
> Unfortunately, it's missed this merge window. It is bad practice to add
> new features to linux-next during a merge window, and it is also bad to
> send new features to Linus without them having been in linux-next before
> the merge window opened.
>
> It will be queued for -rc1.
I mean, it will be queued /after/ -rc1.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2014-12-15 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 6:02 request bitrev patch merge Wang, Yalin
2014-12-15 9:52 ` Russell King - ARM Linux
2014-12-15 10:25 ` Russell King - ARM Linux [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=20141215102554.GC11285@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@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).