From: "Gabriel L. Somlo" <gsomlo@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Karol Gugala <kgugala@antmicro.com>,
Mateusz Holenko <mholenko@antmicro.com>,
Joel Stanley <joel@jms.id.au>, Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>, Lee Jones <lee@kernel.org>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Andrew Davis <afd@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: (subset) [PATCH RFC 0/5] Deprecate register_restart_handler()
Date: Wed, 29 Nov 2023 05:09:57 -0500 [thread overview]
Message-ID: <ZWcN9RNlk4+SB7CO@errol.ini.cmu.edu> (raw)
In-Reply-To: <170110370952.2695179.559211126183016709.b4-ty@kernel.org>
Hi Mark,
On Mon, Nov 27, 2023 at 04:48:29PM +0000, Mark Brown wrote:
> On Fri, 17 Nov 2023 10:10:01 -0600, Andrew Davis wrote:
> > Explanation is in patch #1.
> >
> > The rest of this series is a set of representative examples of converting
> > away from the old API. They should be valid and can be taken by their
> > respective maintainers even if patch #1 doesn't find acceptance.
> >
> > Thanks,
> > Andrew
> >
> > [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [4/5] spi: sprd: adi: Use devm_register_restart_handler()
> commit: 8e6a43961f24cf841d3c0d199521d0b284d948b9
Any chance you can also pick up
[2/5] drivers/soc/litex: Use devm_register_restart_handler()
from this series?
I'm maintaining the LiteX (FPGA SoC) related drivers, but we don't as of
yet have a dedicated "path to upstream" of our own -- we've been mostly
going through specific subsystem trees (e.g. mmc, block, networking, etc.),
for mostly device drivers, up until now...
If not, no worries, I need to dedicate some time to figuring this out
eventually anyway :)
Thanks much,
--Gabriel
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
>
prev parent reply other threads:[~2023-11-29 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 16:10 Andrew Davis
2023-11-17 16:10 ` [PATCH RFC 1/5] kernel/reboot: " Andrew Davis
2023-11-17 16:10 ` [PATCH RFC 2/5] drivers/soc/litex: Use devm_register_restart_handler() Andrew Davis
2023-11-29 10:03 ` Gabriel L. Somlo
2023-12-20 20:35 ` Gabriel L. Somlo
2023-11-17 16:10 ` [PATCH RFC 3/5] power: reset: gpio-restart: Use devm_register_sys_off_handler() Andrew Davis
2023-11-17 16:10 ` [PATCH RFC 4/5] spi: sprd: adi: Use devm_register_restart_handler() Andrew Davis
2023-11-17 16:10 ` [PATCH RFC 5/5] firmware: psci: Use register_sys_off_handler(SYS_OFF_MODE_RESTART) Andrew Davis
2023-11-27 16:48 ` (subset) [PATCH RFC 0/5] Deprecate register_restart_handler() Mark Brown
2023-11-29 10:09 ` Gabriel L. Somlo [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=ZWcN9RNlk4+SB7CO@errol.ini.cmu.edu \
--to=gsomlo@gmail.com \
--cc=afd@ti.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mholenko@antmicro.com \
--cc=orsonzhai@gmail.com \
--cc=sre@kernel.org \
--cc=zhang.lyra@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®