From: Sasha Levin <sashal@kernel.org>
To: Nanyong Sun <sunnanyong@huawei.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: Patch "selftests: mm: fix the incorrect usage() info of khugepaged" has been added to the 6.11-stable tree
Date: Wed, 23 Oct 2024 07:47:00 -0400 [thread overview]
Message-ID: <ZxjiNHPvny8oaVbq@sashalap> (raw)
In-Reply-To: <9a81f472-22ab-c921-ae2e-ec5843be4490@huawei.com>
On Wed, Oct 23, 2024 at 09:22:35AM +0800, Nanyong Sun wrote:
>On 2024/10/23 1:44, Sasha Levin wrote:
>
>>This is a note to let you know that I've just added the patch titled
>>
>> selftests: mm: fix the incorrect usage() info of khugepaged
>>
>>to the 6.11-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:
>> selftests-mm-fix-the-incorrect-usage-info-of-khugepa.patch
>>and it can be found in the queue-6.11 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.
>Hi，
> I don't think this patch needs to be added to the stable tree
>because this just fixes usage
>information, as Andrew had previously said：
>https://lore.kernel.org/lkml/20241017001441.2db5adaaa63dc3faa0934204@linux-foundation.org/
I'll drop it, but really - why not? It's a cheap fix that is very
unlikely to introduce regressions and it improves the user's experience.
--
Thanks,
Sasha
prev parent reply other threads:[~2024-10-23 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241022174426.2836479-1-sashal@kernel.org>
2024-10-23 1:22 ` Patch "selftests: mm: fix the incorrect usage() info of khugepaged" has been added to the 6.11-stable tree Nanyong Sun
2024-10-23 11:47 ` 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=ZxjiNHPvny8oaVbq@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=shuah@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sunnanyong@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