From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Baokun Li <libaokun1@huawei.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: yebin10@huawei.com, yukuai3@huawei.com
Subject: Re: [PATCH -next V5 0/2] fix two bugs when trying rmmod sata_fsl
Date: Fri, 26 Nov 2021 22:27:29 +0300 [thread overview]
Message-ID: <52d961ae-e4e0-00fb-0753-518125edc560@gmail.com> (raw)
In-Reply-To: <4469be5f-01a9-5d10-9dc3-b703f36a1ea4@opensource.wdc.com>
Hello!
On 11/26/21 4:56 AM, Damien Le Moal wrote:
>> V1->V2:
>> Fixed the check on the return value of platform_get_irq().
>> And propagate errors up to sata_fsl_probe()'s callers.
>> V2->V3:
>> Add fixed and CC stable and modified the patch description.
>> V3->V4:
>> Use a single structure.
>> V4->V5:
>> Delete duplicate dev_err() message.
>>
>> Baokun Li (2):
>> sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl
>> sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl
>>
>> drivers/ata/sata_fsl.c | 20 +++++++++++++-------
>> 1 file changed, 13 insertions(+), 7 deletions(-)
>>
>
> The series looks good to me now.
>
> Sergei ? Are you OK with it ?
Yeah, I'll just give the patches by Reviewed-by's.
MBR, Sergei
next prev parent reply other threads:[~2021-11-26 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 2:03 [PATCH -next V5 0/2] fix two bugs when trying rmmod sata_fsl Baokun Li
2021-11-26 1:56 ` Damien Le Moal
2021-11-26 19:27 ` Sergei Shtylyov [this message]
2021-11-26 2:03 ` [PATCH -next V5 1/2] sata_fsl: fix UAF in sata_fsl_port_stop when " Baokun Li
2021-11-26 19:43 ` Sergei Shtylyov
2021-11-27 1:35 ` libaokun (A)
2021-11-26 2:03 ` [PATCH -next V5 2/2] sata_fsl: fix warning in remove_proc_entry " Baokun Li
2021-11-26 19:44 ` Sergei Shtylyov
2021-11-27 1:36 ` libaokun (A)
2021-11-29 11:38 ` [PATCH -next V5 0/2] fix two bugs when trying " Damien Le Moal
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=52d961ae-e4e0-00fb-0753-518125edc560@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=libaokun1@huawei.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yebin10@huawei.com \
--cc=yukuai3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.