From: Olof Johansson <olof@lixom.net>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: kernel@pengutronix.de, Dinh Nguyen <dinguyen@kernel.org>,
arm@kernel.org, linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC, GIT PULL] Late reset controller changes for v5.0
Date: Sat, 12 Jan 2019 22:06:35 -0800 [thread overview]
Message-ID: <20190113060635.7lhatlwwhxedk6d3@localhost> (raw)
In-Reply-To: <1546966907.5406.17.camel@pengutronix.de>
On Tue, Jan 08, 2019 at 06:01:47PM +0100, Philipp Zabel wrote:
> Dear arm-soc maintainers,
>
> due to a combination of a late merge conflict, early holidays, and the
> common cold, I have failed to send the last reset controller pull
> request in time for the v5.0-rc1 merge window. As usual there are not
> many changes, and they have been carried in linux-next for quite a
> while.
>
> One of the changes, commit b3ca9888f35f ("reset: socfpga: add an early
> reset driver for SoCFPGA") is necessary for the Stratix10 platform to
> boot, since the already merged change 8bb4f3f55961 ("arm64: dts:
> stratix10: use "altr,stratix10-rst-mgr" binding") depends on it.
>
> Can you take the whole lot for v5.0-rc2? Should I split out the SoCFPGA
> early reset patch + the NULL pointer dereference fix into a separate
> "fixes" pull request for v5.0-rc2, postponing the other patches to for-
> v5.1? Or do we have to revert 8bb4f3f55961 for now? Please advise.
Hi,
Unfortunate, but looking at the set of patches, it's also not a whole lot of
code. Based on the list, nothing looks particularly high risk.
I've merged the lot into our fixes branch.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-13 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 17:01 [RFC, GIT PULL] Late reset controller changes for v5.0 Philipp Zabel
2019-01-13 6:06 ` Olof Johansson [this message]
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=20190113060635.7lhatlwwhxedk6d3@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=dinguyen@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
/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).