From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] UEFI support for 32-bit ARM
Date: Sat, 2 Jan 2016 12:04:12 +0000 [thread overview]
Message-ID: <20160102120410.GV8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKv+Gu_Kwx7iOMFcUPEd5ORxn5=-qKuE7mGniCvoLbAqRbhK6w@mail.gmail.com>
On Tue, Dec 29, 2015 at 08:40:33AM +0100, Ard Biesheuvel wrote:
> On 22 December 2015 at 13:54, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Tue, Dec 22, 2015 at 01:51:23PM +0100, Ard Biesheuvel wrote:
> >> 29 files changed, 986 insertions(+), 368 deletions(-)
> >
> > Thanks, that now matches.
> >
>
> I suppose the fact that none of this has turned up in -next implies
> that it will not make v4.5?
I pulled it into my devel-testing branch on 22nd, which is the
pre-cursor to it appearing in devel-stable (devel-stable is for
stuff which has passed my testing.) I never got around to
merging it into devel-stable prior to the Christmas break.
I suspect even if I did publish it, we'd find that -next wouldn't
have picked it up - just before I took a break, I merged the PL011
changes which would conflict with those which GregKH incorrectly
picked up, and I know that linux-next hasn't reported any conflicts.
Ergo, linux-next has taken a break over the christmas period as well.
If Linus decides to do -rc8 tomorrow, I'll merge it into devel-stable
and it'll appear in -next.
Even if I merge it into my for-next branch _now_, it won't appear in
-next prior to Monday, and so if Sunday sees the release of v4.4, it
won't have been in -next prior to the merge window, and will be dodgy
to send to Linus (Linus sometimes compares what he merges against
linux-next.)
So... I'll decide on Monday what to do.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2016-01-02 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 17:10 [GIT PULL] UEFI support for 32-bit ARM Ard Biesheuvel
2015-12-14 17:18 ` Will Deacon
2015-12-22 12:21 ` Ard Biesheuvel
2015-12-22 12:31 ` Russell King - ARM Linux
2015-12-22 12:36 ` Ard Biesheuvel
2015-12-22 12:36 ` Russell King - ARM Linux
2015-12-22 12:51 ` Ard Biesheuvel
2015-12-22 12:54 ` Russell King - ARM Linux
2015-12-29 7:40 ` Ard Biesheuvel
2016-01-02 12:04 ` 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=20160102120410.GV8644@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).