From: <Conor.Dooley@microchip.com>
To: <yangyingliang@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Cc: <Daire.McNamara@microchip.com>, <broonie@kernel.org>
Subject: Re: [PATCH -next v2 0/3] spi: microchip-core: fix and cleanups
Date: Wed, 13 Jul 2022 07:03:14 +0000 [thread overview]
Message-ID: <f6280aaa-51ab-1857-59ae-2ba2ed03f24b@microchip.com> (raw)
In-Reply-To: <20220713025657.3524506-1-yangyingliang@huawei.com>
On 13/07/2022 03:56, Yang Yingliang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Patch #1 fix a UAF in mchp_corespi_remove().
> Patch #2 and #3 some cleanups to simpify code.
P sure I already gave you an R-b for patch 1, but for the series:
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> v1 -> v2:
> add patch #3 to use dev_err_probe to simpify code.
>
> Yang Yingliang (3):
> spi: microchip-core: fix UAF in mchp_corespi_remove()
> spi: microchip-core: switch to use devm_spi_alloc_master()
> spi: microchip-core: switch to use dev_err_probe()
>
> drivers/spi/spi-microchip-core.c | 56 ++++++++++++--------------------
> 1 file changed, 20 insertions(+), 36 deletions(-)
>
> --
> 2.25.1
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-07-13 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 2:56 [PATCH -next v2 0/3] spi: microchip-core: fix and cleanups Yang Yingliang
2022-07-13 2:56 ` [PATCH -next v2 1/3] spi: microchip-core: fix UAF in mchp_corespi_remove() Yang Yingliang
2022-07-13 2:56 ` [PATCH -next v2 2/3] spi: microchip-core: switch to use devm_spi_alloc_master() Yang Yingliang
2022-07-13 2:56 ` [PATCH -next v2 3/3] spi: microchip-core: switch to use dev_err_probe() Yang Yingliang
2022-07-13 7:03 ` Conor.Dooley [this message]
2022-07-13 14:19 ` [PATCH -next v2 0/3] spi: microchip-core: fix and cleanups Mark Brown
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=f6280aaa-51ab-1857-59ae-2ba2ed03f24b@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=yangyingliang@huawei.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