From: Miquel Raynal <miquel.raynal@bootlin.com>
To: ZhaoLong Wang <wangzhaolong1@huawei.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
dpervushin <dpervushin@embeddedalley.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
chengzhihao1 <chengzhihao1@huawei.com>,
yi zhang <yi.zhang@huawei.com>, yangerkun <yangerkun@huawei.com>
Subject: Re: [PATCH v3] mtd: Fix gluebi NULL pointer dereference caused by ftl notifier
Date: Tue, 19 Dec 2023 15:44:38 +0100 [thread overview]
Message-ID: <20231219154438.2bc1820e@xps-13> (raw)
In-Reply-To: <04b4c375-d890-9458-5d62-0a9ba74b8c68@huawei.com>
Hi ZhaoLong,
wangzhaolong1@huawei.com wrote on Tue, 19 Dec 2023 22:36:50 +0800:
> Friendly ping...
>
> I'd like to know what the current status of this patch is. Is there a need for further programme improvements?
Easy, see below.
>
> Bast regards,
> ZhaoLong Wang
>
>
> > ----- Ursprüngliche Mail -----
> >> Von: "Miquel Raynal" <miquel.raynal@bootlin.com>
> >> Ack. I'll queue this once the log fixed and your official Ack-by
> >> received for mtd/next after -rc1 is out.
Here I depict two conditions.
> > Acked-by: Richard Weinberger <richard@nod.at>
And here one of them is fulfilled, which means the other one is still
not AFAIK :)
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-12-19 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 1:20 [PATCH v3] mtd: Fix gluebi NULL pointer dereference caused by ftl notifier ZhaoLong Wang
2023-10-27 3:23 ` Zhihao Cheng
2023-10-27 17:40 ` Miquel Raynal
2023-10-27 20:30 ` Richard Weinberger
2023-10-29 13:50 ` Miquel Raynal
2023-10-29 15:39 ` Richard Weinberger
2023-12-19 14:36 ` ZhaoLong Wang
2023-12-19 14:44 ` Miquel Raynal [this message]
2023-12-20 2:15 ` ZhaoLong Wang
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=20231219154438.2bc1820e@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=chengzhihao1@huawei.com \
--cc=dpervushin@embeddedalley.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=wangzhaolong1@huawei.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@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