From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] Broadcom defconfig-arm64 changes for 4.9 (part 2)
Date: Mon, 24 Oct 2016 09:52:59 -0700 [thread overview]
Message-ID: <a8e6638c-95a1-6847-dc75-368b69b7a87c@gmail.com> (raw)
In-Reply-To: <CAOesGMjJ3_rPUke8B5yW_6Q4NyP1sb-wqY5jfcs1_+UhGQK9_g@mail.gmail.com>
On 10/23/2016 04:50 PM, Olof Johansson wrote:
> On Sun, Oct 23, 2016 at 2:55 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 09/30/2016 12:23 PM, Florian Fainelli wrote:
>>> The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
>>>
>>> Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
>>>
>>> are available in the git repository at:
>>>
>>> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.9/defconfig-arm64
>>>
>>> for you to fetch changes up to 51e3fb1d3f514cd336faf185df73b25fca194773:
>>>
>>> Merge tag 'bcm2835-defconfig-64-next-2016-09-22' into defconfig-arm64/next (2016-09-30 12:02:29 -0700)
>>>
>>> ----------------------------------------------------------------
>>> This pull request contains Broadcom ARM64-based SoCs defconfig changes for 4.9,
>>> please pull the following changes:
>>>
>>> - Eric updates the ARMv8 defconfig to contain everything that is needed to run
>>> a 64-bit kernel on the Raspberry Pi 3
>>>
>>> ----------------------------------------------------------------
>>> Eric Anholt (1):
>>> arm64: Add BCM2835 (Raspberry Pi 3) support to the defconfig
>>>
>>> Florian Fainelli (1):
>>> Merge tag 'bcm2835-defconfig-64-next-2016-09-22' into defconfig-arm64/next
>>>
>>> arch/arm64/configs/defconfig | 16 ++++++++++++++++
>>> 1 file changed, 16 insertions(+)
>>
>> Arnd, Kevin, Olof,
>>
>> Following Olof's response here:
>>
>> https://www.spinics.net/lists/arm-kernel/msg534687.html
>>
>> do you think we could merge these for 4.9-rcX? Let me know if I should
>> send a fresh pull request for that.
>
> Main reason to respin would be if you need to rebase due to other
> changes that have gone in, or if you expect to have other material
> that should be based on a 4.9-rc base.
No dependencies, this should apply cleanly to 4.9-rc. Thanks!
--
Florian
next prev parent reply other threads:[~2016-10-24 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 19:23 [GIT PULL 1/4] Broadcom devicetree changes for 4.9 (part 2) Florian Fainelli
2016-09-30 19:23 ` [GIT PULL 2/4] Broadcom devicetree-arm64 " Florian Fainelli
2016-09-30 19:23 ` [GIT PULL 3/4] Broadcom defconfig " Florian Fainelli
2016-09-30 19:23 ` [GIT PULL 4/4] Broadcom defconfig-arm64 " Florian Fainelli
2016-10-23 21:55 ` Florian Fainelli
2016-10-23 23:50 ` Olof Johansson
2016-10-24 16:52 ` Florian Fainelli [this message]
2016-10-03 5:28 ` [GIT PULL 1/4] Broadcom devicetree " 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=a8e6638c-95a1-6847-dc75-368b69b7a87c@gmail.com \
--to=f.fainelli@gmail.com \
--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).