From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 4.11
Date: Wed, 18 Jan 2017 16:31:20 -0800 [thread overview]
Message-ID: <20170119003120.GN23725@localhost> (raw)
In-Reply-To: <1c3325d4-dfcc-4723-89be-94d0adc2f3f3@gmail.com>
On Tue, Jan 17, 2017 at 05:32:22PM -0800, Florian Fainelli wrote:
> On 01/17/2017 05:29 PM, Florian Fainelli wrote:
> > The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
> >
> > Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
>
> Forgot to mention that, but this is against v4.10-rc2, because v4.10-rc1
> just was not building on ARM64, thanks!
Yep, that's fine, We're at -rc3 on our branches this release.
-Olof
next prev parent reply other threads:[~2017-01-19 0:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:29 [GIT PULL 1/2] Broadcom devicetree changes for 4.11 Florian Fainelli
2017-01-18 1:29 ` [GIT PULL 2/2] Broadcom devicetree-arm64 " Florian Fainelli
2017-01-18 1:32 ` Florian Fainelli
2017-01-19 0:31 ` Olof Johansson [this message]
2017-01-19 0:30 ` Olof Johansson
2017-01-19 0:30 ` [GIT PULL 1/2] Broadcom devicetree " Olof Johansson
2017-01-19 1:25 ` [GIT PULL 1/2] Broadcom devicetree changes for 4.11 (try 2) Florian Fainelli
2017-01-20 0:25 ` Olof Johansson
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=20170119003120.GN23725@localhost \
--to=olof@lixom.net \
--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).