From: Florian Fainelli <f.fainelli@gmail.com>
To: arm@kernel.org
Cc: thierry.reding@gmail.com, sudeep.holla@arm.com,
Florian Fainelli <f.fainelli@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
bcm-kernel-feedback-list@broadcom.com (maintainer:BROADCOM
BCM7XXX ARM ARCHITECTURE),
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM7XXX ARM ARCHITECTURE),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 0/2] soc: brcmstb: Fix multi-platform issues
Date: Fri, 12 Jan 2018 13:08:13 -0800 [thread overview]
Message-ID: <20180112210815.9684-1-f.fainelli@gmail.com> (raw)
Hi,
This incorporates Sudeep's and Thierry's changes and makes minor tweaks
such that we don't return errors from initcalls even if we are not
running on Broadcom STB platforms.
I kept your authorship because you did 99% of the work, and I just added a
proper Fixes: tag to the first patch and combined Thierry's 4 patches into one.
This has now been properly tested by booting a QEMU ARM virtual machine to verify
we are not seeing BRCMSTB related messages anymore.
Again, sorry for missing the multi-platform kernel case!
Thank you!
Sudeep Holla (1):
soc: brcmstb: biuctrl: exit without warning on non brcmstb platforms
Thierry Reding (1):
soc: bcm: brcmstb: Be multi-platform compatible
drivers/soc/bcm/brcmstb/biuctrl.c | 20 +++++++++++---------
drivers/soc/bcm/brcmstb/common.c | 38 +++++++++++++++++++++++++++++---------
2 files changed, 40 insertions(+), 18 deletions(-)
--
2.14.1
next reply other threads:[~2018-01-12 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 21:08 Florian Fainelli [this message]
2018-01-12 21:08 ` [PATCH 1/2] soc: brcmstb: biuctrl: exit without warning on non brcmstb platforms Florian Fainelli
2018-01-12 21:08 ` [PATCH 2/2] soc: bcm: brcmstb: Be multi-platform compatible Florian Fainelli
2018-01-15 14:47 ` 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=20180112210815.9684-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=thierry.reding@gmail.com \
/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
all inboxes | Powered by JetHome®