From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] ARM: multi_v7_defconfig: Add more Broadcom SoCs
Date: Fri, 20 May 2016 12:07:25 -0700 [thread overview]
Message-ID: <1463771252-12805-1-git-send-email-f.fainelli@gmail.com> (raw)
This patch series enables more fundamental drivers which are useful for
Broadcom BCM63xx and BCM7xxx SoCs.
The last patch remove bcm_defconfig which is causing a whole lot of confusiong
at best and is completely out of sync now.
Florian Fainelli (7):
ARM: multi_v7_defconfig: Enable BCM63xx
ARM: multi_v7_defconfig: Enable BRCMSTB networking
ARM: multi_v7_defconfig: Enable BRCMSTB AHCI
ARM: multi_v7_defconfig: Enable BCM7038 Watchdog
ARM: multi_v7_defconfig: Enable Broadcom STB PWM
ARM: multi_v7_defconfig: Enable Broadcom Kona watchdog
ARM: Remove bcm_defconfig
arch/arm/configs/bcm_defconfig | 142 ------------------------------------
arch/arm/configs/multi_v7_defconfig | 13 ++++
2 files changed, 13 insertions(+), 142 deletions(-)
delete mode 100644 arch/arm/configs/bcm_defconfig
--
2.7.4
next reply other threads:[~2016-05-20 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 19:07 Florian Fainelli [this message]
2016-05-20 19:07 ` [PATCH 1/7] ARM: multi_v7_defconfig: Enable BCM63xx Florian Fainelli
2016-05-20 19:07 ` [PATCH 2/7] ARM: multi_v7_defconfig: Enable BRCMSTB networking Florian Fainelli
2016-05-20 19:07 ` [PATCH 3/7] ARM: multi_v7_defconfig: Enable BRCMSTB AHCI Florian Fainelli
2016-05-20 19:07 ` [PATCH 4/7] ARM: multi_v7_defconfig: Enable BCM7038 Watchdog Florian Fainelli
2016-05-20 19:07 ` [PATCH 5/7] ARM: multi_v7_defconfig: Enable Broadcom STB PWM Florian Fainelli
2016-05-20 19:07 ` [PATCH 6/7] ARM: multi_v7_defconfig: Enable Broadcom Kona watchdog Florian Fainelli
2016-05-20 19:07 ` [PATCH 7/7] ARM: Remove bcm_defconfig Florian Fainelli
2016-05-20 20:36 ` [PATCH 0/7] ARM: multi_v7_defconfig: Add more Broadcom SoCs Scott Branden
2016-05-31 18:04 ` 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=1463771252-12805-1-git-send-email-f.fainelli@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).