From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
rdunlap@infradead.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, paul.gortmaker@windriver.com
Subject: [PATCH reset-next 0/2] reset: brcmstb: Misc fixes
Date: Tue, 22 Jan 2019 16:33:43 -0800 [thread overview]
Message-ID: <20190123003345.13750-1-f.fainelli@gmail.com> (raw)
Hi Philipp,
These two patches fix some recent issues brought up by Paul and Randy,
feel free to squash into c196cdc7659d ("reset: Add Broadcom STB SW_INIT
reset controller driver") since this is only in reset/next and
linux-next so far.
Thank you!
Florian Fainelli (2):
reset: brcmstb: Make it tristate
reset: brcmstb: Fix 32-bit build with 64-bit resource_size_t
drivers/reset/Kconfig | 3 ++-
drivers/reset/reset-brcmstb.c | 6 ++++--
2 files changed, 6 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-23 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 0:33 Florian Fainelli [this message]
2019-01-23 0:33 ` [PATCH reset-next 1/2] reset: brcmstb: Make it tristate Florian Fainelli
2019-01-23 0:33 ` [PATCH reset-next 2/2] reset: brcmstb: Fix 32-bit build with 64-bit resource_size_t Florian Fainelli
2019-01-23 0:53 ` Randy Dunlap
2019-01-23 9:39 ` Philipp Zabel
2019-01-23 14:23 ` David Laight
2019-01-23 9:41 ` [PATCH reset-next 0/2] reset: brcmstb: Misc fixes Philipp Zabel
2019-01-23 22:56 ` 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=20190123003345.13750-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).