From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 6/7] Broadcom defconfig changes for 4.8 Part 1
Date: Sun, 19 Jun 2016 22:54:16 -0700 [thread overview]
Message-ID: <20160620055416.GI2329@localhost> (raw)
In-Reply-To: <1466128575-5378-6-git-send-email-f.fainelli@gmail.com>
On Thu, Jun 16, 2016 at 06:56:14PM -0700, Florian Fainelli wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
>
> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>
> are available in the git repository at:
>
> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/defconfig
>
> for you to fetch changes up to 41463c3e6eae3dfa4377069966ed02b4ba378e79:
>
> ARM: Remove bcm_defconfig (2016-06-16 13:40:49 -0700)
>
> ----------------------------------------------------------------
> This pull request contains defconfig changes for Broadcom ARM-based SoCs:
>
> - Florian enables support for the BCM63xx DSL SoCs basic peripherals, enables
> the networking subsystems for Set Top Box SoCs, enables the PWM, watchdog and
> the AHCI controller and SATA PHY drivers
>
> - Florian removes the bcm_defconfig file which is no longer useful and updates
> multi_v7_defconfig to include the Kona watchdog to provide proper reboot for the
> Broadcom Kona platforms
>
> Please note that Tejun Heo has queued a patch which renames AHCI_BRCMSTB into
> AHCI_BRCM, to avoid two patches in a row, we just enable AHCI_BRCM to be future
> proof
So, you say that bcm_defconfig is no longer useful. While I'm happy to see the
number of defconfigs go down, I'd like to clarify that we do still see per-SoC
defconfigs somewhat useful, in that they are a lot closer to what someone would
want to use for defconfig in a product kernel based on the SoC. It's easier to
start from the SoC-specific defconfig and remove pieces that aren't needed than
to start from multi_v7_defconfig.
That being said, I'm happy to remove it if you think that's what works best for
your platform.
Merged into next/defconfig.
-Olof
next prev parent reply other threads:[~2016-06-20 5:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 1:56 [GIT PULL 1/7] Broadcom soc changes for 4.8 Part 1 Florian Fainelli
2016-06-17 1:56 ` [GIT PULL 2/7] Broadcom soc-arm64 " Florian Fainelli
2016-06-20 5:44 ` Olof Johansson
2016-06-17 1:56 ` [GIT PULL 3/7] Broadcom devicetree " Florian Fainelli
2016-06-20 5:45 ` Olof Johansson
2016-06-17 1:56 ` [GIT PULL 4/7] Broadcom devicetree-arm64 " Florian Fainelli
2016-06-20 5:48 ` Olof Johansson
2016-06-17 1:56 ` [GIT PULL 5/7] Broadcom maintainers " Florian Fainelli
2016-06-20 5:51 ` Olof Johansson
2016-06-20 7:35 ` Rafał Miłecki
2016-06-20 7:47 ` Arnd Bergmann
2016-06-20 15:30 ` Olof Johansson
2016-06-20 21:33 ` Scott Branden
2016-06-17 1:56 ` [GIT PULL 6/7] Broadcom defconfig " Florian Fainelli
2016-06-20 5:54 ` Olof Johansson [this message]
2016-06-20 21:43 ` Scott Branden
2016-06-20 21:51 ` Florian Fainelli
2016-06-20 22:04 ` Olof Johansson
2016-06-20 22:25 ` Scott Branden
2016-06-17 1:56 ` [GIT PULL 7/7] Broadcom drivers " Florian Fainelli
2016-06-20 5:55 ` Olof Johansson
2016-06-20 5:43 ` [GIT PULL 1/7] Broadcom soc " 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=20160620055416.GI2329@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).