From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Broadcom defconfig fixes for 4.10
Date: Mon, 16 Jan 2017 22:08:49 -0800 [thread overview]
Message-ID: <20170117060849.GE16607@localhost> (raw)
In-Reply-To: <20170115023637.24759-1-f.fainelli@gmail.com>
On Sat, Jan 14, 2017 at 06:36:36PM -0800, Florian Fainelli wrote:
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
>
> Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
>
> are available in the git repository at:
>
> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.10/defconfig-fixes
>
> for you to fetch changes up to 91546c56624a79f4a8fd80bede6b5a38c0f0ad78:
>
> ARM: multi_v7_defconfig: set bcm47xx watchdog (2017-01-12 16:03:12 -0800)
>
> ----------------------------------------------------------------
> This pull request contains fixes to multi_v7_defconfig for Broadcom ARM-based
> SoCs, please pull the following changes:
>
> - Valenting fixes two incorrect Kconfig symbols for BCM47xx: NVRAM and watchdog drivers
>
> ----------------------------------------------------------------
> Valentin Rothberg (2):
> ARM: multi_v7_defconfig: fix config typo
> ARM: multi_v7_defconfig: set bcm47xx watchdog
Merged. How did we even get here? Did the options rename or did someone
edit config files by hand?
-Olof
next prev parent reply other threads:[~2017-01-17 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 2:36 [GIT PULL 2/2] Broadcom defconfig fixes for 4.10 Florian Fainelli
2017-01-15 2:36 ` [GIT PULL 1/2] Broadcom arm Device Tree " Florian Fainelli
2017-01-17 6:09 ` Olof Johansson
2017-01-17 6:08 ` Olof Johansson [this message]
2017-01-17 18:57 ` [GIT PULL 2/2] Broadcom defconfig " Florian Fainelli
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=20170117060849.GE16607@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).