From: Peng Ma <peng.ma@nxp.com>
To: Mark Brown <broonie@kernel.org>, Leo Li <leoyang.li@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: RE: [EXT] Re: [PATCH] spi: spi-fsl-dspi: Adding shutdown hook
Date: Mon, 27 Apr 2020 02:35:49 +0000 [thread overview]
Message-ID: <AM7PR04MB7016C9550F95541971A7EE89EDAF0@AM7PR04MB7016.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <158773300537.30241.1154325901954580764.b4-ty@kernel.org>
Hi Mark,
>-----Original Message-----
>From: Mark Brown <broonie@kernel.org>
>Sent: 2020年4月24日 20:57
>To: Leo Li <leoyang.li@nxp.com>; Peng Ma <peng.ma@nxp.com>
>Cc: linux-kernel@vger.kernel.org; linux-spi@vger.kernel.org
>Subject: [EXT] Re: [PATCH] spi: spi-fsl-dspi: Adding shutdown hook
>
>Caution: EXT Email
>
>On Fri, 24 Apr 2020 14:12:16 +0800, Peng Ma wrote:
>> We need to ensure dspi controller could be stopped in order for kexec
>> to start the next kernel.
>> So add the shutdown operation support.
>>
>> Signed-off-by: Peng Ma <peng.ma@nxp.com>
>> ---
>> drivers/spi/spi-fsl-dspi.c | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> [...]
>
>Applied to
>
>
>https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kerne
>l.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fbroonie%2Fspi.git&data
>=02%7C01%7Cpeng.ma%40nxp.com%7C1cae36a19be74172501c08d7e84ef418
>%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637233298112661854
>&sdata=7WllSlzlH5AtoQ4T8DvvI7GCysPmXivnu4A8aghUxys%3D&reser
>ved=0 for-5.8
>
>Thanks!
>
>[1/1] spi: spi-fsl-dspi: Adding shutdown hook
> commit: dc234825997ec6ff05980ca9e2204f4ac3f8d695
>
>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.
>
[Peng Ma] OK, Got it, thanks very much!
Best Regards,
Peng
>Thanks,
>Mark
prev parent reply other threads:[~2020-04-27 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 6:12 Peng Ma
2020-04-24 12:56 ` Mark Brown
2020-04-27 2:35 ` Peng Ma [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=AM7PR04MB7016C9550F95541971A7EE89EDAF0@AM7PR04MB7016.eurprd04.prod.outlook.com \
--to=peng.ma@nxp.com \
--cc=broonie@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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
all inboxes | Powered by JetHome®