From: Sasha Levin <sashal@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: stable-commits@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
stable@vger.kernel.org
Subject: Re: Patch "iommu/amd: Simplify pagetable freeing" has been added to the 5.15-stable tree
Date: Mon, 7 Mar 2022 05:58:50 -0500 [thread overview]
Message-ID: <YiXlamFo/eqTYDeX@sashalap> (raw)
In-Reply-To: <34442eae-a30d-5144-0fc5-edee35bee7b9@arm.com>
On Mon, Mar 07, 2022 at 10:35:19AM +0000, Robin Murphy wrote:
>On 2022-03-05 21:00, Sasha Levin wrote:
>>This is a note to let you know that I've just added the patch titled
>>
>> iommu/amd: Simplify pagetable freeing
>>
>>to the 5.15-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>>The filename of the patch is:
>> iommu-amd-simplify-pagetable-freeing.patch
>>and it can be found in the queue-5.15 subdirectory.
>>
>>If you, or anyone else, feels it should not be added to the stable tree,
>>please let <stable@vger.kernel.org> know about it.
>
>I don't think this one qualifies for stable - it was just a
>refactoring to aid future development. The "fixing" of types is merely
>cosmetic, and the code size benefit was just a little bonus, hardly
>significant.
I took it and "iommu/amd: Use put_pages_list" to avoid the conflict when
taking 6b0b2d9a6a30 ("iommu/amd: Fix I/O page table memory leak").
Let me see if I can rework it to not need the 2 prereq patches...
--
Thanks,
Sasha
prev parent reply other threads:[~2022-03-07 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220305210025.146536-1-sashal@kernel.org>
2022-03-07 10:35 ` Patch "iommu/amd: Simplify pagetable freeing" has been added to the 5.15-stable tree Robin Murphy
2022-03-07 10:58 ` Sasha Levin [this message]
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=YiXlamFo/eqTYDeX@sashalap \
--to=sashal@kernel.org \
--cc=joro@8bytes.org \
--cc=robin.murphy@arm.com \
--cc=stable-commits@vger.kernel.org \
--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