From: Philipp Zabel <p.zabel@pengutronix.de>
To: soc@kernel.org
Cc: kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Reset controller fixes for v5.6
Date: Mon, 17 Feb 2020 10:09:47 +0100 [thread overview]
Message-ID: <e6eaa409883cbae8d1e818b732b98c3362635712.camel@pengutronix.de> (raw)
Dear SoC maintainers,
The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
are available in the Git repository at:
git://git.pengutronix.de/git/pza/linux.git tags/reset-fixes-for-v5.6
for you to fetch changes up to b460e0a9e2404450a0cc4c5e6476483d6cda1b26:
reset: intel: add unspecified HAS_IOMEM dependency (2020-02-10 11:11:55 +0100)
----------------------------------------------------------------
Reset controller fixes for v5.6
Fix the intel,rcu-gw binding schema for the intel,global-reset
property, fix whitespace in the MAINTAINERS keyword entry, and
add missing CONFIG_HAS_IOMEM dependency to CONFIG_RESET_INTEL_GW
and CONFIG_RESET_BRCMSTB_RESCAL.
----------------------------------------------------------------
Brendan Higgins (2):
reset: brcmstb-rescal: add unspecified HAS_IOMEM dependency
reset: intel: add unspecified HAS_IOMEM dependency
Lukas Bulwahn (1):
MAINTAINERS: fix style in RESET CONTROLLER FRAMEWORK
Rob Herring (1):
dt-bindings: reset: intel,rcu-gw: Fix intel,global-reset schema
Documentation/devicetree/bindings/reset/intel,rcu-gw.yaml | 6 +++++-
MAINTAINERS | 2 +-
drivers/reset/Kconfig | 3 ++-
3 files changed, 8 insertions(+), 3 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-02-17 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 9:09 Philipp Zabel [this message]
2020-03-03 21:31 ` [GIT PULL] Reset controller fixes for v5.6 Rob Herring
2020-03-03 22:59 ` 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=e6eaa409883cbae8d1e818b732b98c3362635712.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.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).