From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] Broadcom defconfig changes for 4.15
Date: Mon, 30 Oct 2017 11:02:51 +0100 [thread overview]
Message-ID: <CAK8P3a29z6tNstYRgH8EaCwUhN4rz+YPrUV_XuuPB+Mq41gu8w@mail.gmail.com> (raw)
In-Reply-To: <20171021001636.17662-4-f.fainelli@gmail.com>
On Sat, Oct 21, 2017 at 2:16 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
>
> Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
>
> are available in the git repository at:
>
> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.15/defconfig
>
> for you to fetch changes up to 675a157c61f756affbbc2569c55dc5719342081b:
>
> ARM: multi_v7_defconfig: Enable CONFIG_ARCH_BCM_HR2 (2017-10-12 11:32:43 -0700)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoCs multi_v7_defconfig file
> updates for 4.15, please pull the following:
>
> - Florian enables the Broadcom Hurricane 2 SoC in multi_v7_defconfig
> (CONFIG_ARCH_BCM_HR2)
Pulled into next/soc, thanks!
Arnd
next prev parent reply other threads:[~2017-10-30 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 0:16 [GIT PULL 1/5] Broadcom soc changes for 4.15 (part 2) Florian Fainelli
2017-10-21 0:16 ` [GIT PULL 2/5] Broadcom devicetree changes for 4.15 Florian Fainelli
2017-10-30 12:13 ` Arnd Bergmann
2017-10-21 0:16 ` [GIT PULL 3/5] Broadcom maintainers " Florian Fainelli
2017-10-30 10:18 ` Arnd Bergmann
2017-10-21 0:16 ` [GIT PULL 4/5] Broadcom defconfig " Florian Fainelli
2017-10-30 10:02 ` Arnd Bergmann [this message]
2017-10-21 0:16 ` [GIT PULL 5/5] Broadcom drivers changes for 4.15 (part 2) Florian Fainelli
2017-11-02 15:22 ` Arnd Bergmann
2017-10-30 10:08 ` [GIT PULL 1/5] Broadcom soc " Arnd Bergmann
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=CAK8P3a29z6tNstYRgH8EaCwUhN4rz+YPrUV_XuuPB+Mq41gu8w@mail.gmail.com \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.