From: Greg KH <greg@kroah.com>
To: "Yee Lee (李建誼)" <Yee.Lee@mediatek.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patrick.wang.shcn@gmail.com" <patrick.wang.shcn@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 5.15.y] Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"
Date: Thu, 8 Sep 2022 19:06:36 +0200 [thread overview]
Message-ID: <YxohHANX6omfC27d@kroah.com> (raw)
In-Reply-To: <SI2PR03MB57538512401A213D21B7882C90419@SI2PR03MB5753.apcprd03.prod.outlook.com>
On Wed, Sep 07, 2022 at 08:37:56AM +0000, Yee Lee (李建誼) wrote:
> The commit ids are listed.
>
> Linus tree: 23c2d497de21f25898fbea70aeb292ab8acc8c94
> Linux-5.19.y: 23c2d497de21f25898fbea70aeb292ab8acc8c94
> Linux-5.18.y: 23c2d497de21f25898fbea70aeb292ab8acc8c94
>
> (backported)
> Linux-5.17.y: 0d2e07c04c7f7d83c75c56da3e2f970c5653ade0
> Linux-5.15.y: 70ea5e7b38c30b60821e432abde6f3c359224139
> Linux-5.10.y: 06c348fde545ec90e25de3e5bc4b814bff70ae9f
> Linux-5.4.y: 534d0aebe164fe9afff2a58fb1d5fb458d8a036b
> Linux-4.19.y: 7f4f020286e0bd4aaf40512c80c63a5e5bd629bc
> Linux-4.14.y: 07f108f15fd75a9bff704eed718cc12f91b080dc
> Linux-4.9.y: 96eb48099a7e740768d215a989b26e0af7381371
Thanks, now queued up everywhere.
greg k-h
next prev parent reply other threads:[~2022-09-08 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 7:03 [PATCH 5.15.y] Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()" yee.lee
2022-09-06 12:08 ` Greg KH
2022-09-07 8:37 ` Yee Lee (李建誼)
2022-09-08 17:06 ` Greg KH [this message]
2022-09-08 17:09 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 4.9-stable tree gregkh
2022-09-08 17:09 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 4.14-stable tree gregkh
2022-09-08 17:10 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 4.19-stable tree gregkh
2022-09-08 17:10 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 5.4-stable tree gregkh
2022-09-08 17:10 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 5.10-stable tree gregkh
2022-09-08 17:10 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 5.15-stable tree gregkh
2022-09-08 17:11 ` Patch "Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"" has been added to the 5.19-stable tree gregkh
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=YxohHANX6omfC27d@kroah.com \
--to=greg@kroah.com \
--cc=Yee.Lee@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=patrick.wang.shcn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).