From: Sasha Levin <sashal@kernel.org>
To: "Lin Gui (桂林)" <Lin.Gui@mediatek.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Yongdong Zhang (张永东)" <Yongdong.Zhang@mediatek.com>,
"Bo Ye (叶波)" <Bo.Ye@mediatek.com>,
"Qilin Tan (谭麒麟)" <Qilin.Tan@mediatek.com>
Subject: Re: backport a patch for Linux kernel-5.10 and 6.6 stable tree
Date: Sat, 16 Mar 2024 05:21:30 -0400 [thread overview]
Message-ID: <ZfVkmm5-Ja8ub-i8@sashalap> (raw)
In-Reply-To: <PSAPR03MB565326FF3D69B95B7A5897D7952F2@PSAPR03MB5653.apcprd03.prod.outlook.com>
On Sat, Mar 16, 2024 at 08:16:30AM +0000, Lin Gui (桂林) wrote:
>Hi reviewers,
>
>I suggest to backport a commit to Linux kernel-5.10 and 6.6 stable tree.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/mmc/core/mmc.c?h=v6.8&id=e4df56ad0bf3506c5189abb9be83f3bea05a4c4f
Why? What bug does this fix?
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-03-16 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PSAPR03MB5653FFA63E972A80A6A2F4AF952F2@PSAPR03MB5653.apcprd03.prod.outlook.com>
2024-03-16 8:16 ` backport a patch for Linux kernel-5.10 and 6.6 stable tree Lin Gui (桂林)
2024-03-16 9:21 ` Sasha Levin [this message]
2024-03-18 7:46 ` 回复: " Lin Gui (桂林)
2024-03-18 18:59 ` Greg KH
2024-05-23 2:39 ` backport a patch for Linux kernel-5.15 kernel-6.1 kenrel-6.6 " Lin Gui (桂林)
2024-05-23 6:32 ` Greg KH
[not found] ` <PSAPR03MB565389D72939161224B110CE95F42@PSAPR03MB5653.apcprd03.prod.outlook.com>
2024-05-23 6:49 ` 回复: " Greg KH
[not found] ` <PSAPR03MB5653135ABCAF08A979BCCE0295F42@PSAPR03MB5653.apcprd03.prod.outlook.com>
2024-05-23 11:01 ` 回复: " Greg KH
[not found] ` <PSAPR03MB5653638EEC15BE49B2E03E9495F52@PSAPR03MB5653.apcprd03.prod.outlook.com>
2024-05-24 4:08 ` 回复: " Greg KH
2024-05-24 4:08 ` Greg KH
2024-05-24 5:58 ` 回复: " Lin Gui (桂林)
2024-05-24 6:55 ` Greg KH
2024-05-26 2:51 ` 回复: " Lin Gui (桂林)
2024-06-12 12:08 ` Greg KH
2024-06-12 12:20 ` Greg KH
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=ZfVkmm5-Ja8ub-i8@sashalap \
--to=sashal@kernel.org \
--cc=Bo.Ye@mediatek.com \
--cc=Lin.Gui@mediatek.com \
--cc=Qilin.Tan@mediatek.com \
--cc=Yongdong.Zhang@mediatek.com \
--cc=stable@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 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.