From: Greg KH <gregkh@linuxfoundation.org>
To: Yifei Liu <yifei.l.liu@oracle.com>
Cc: "shuah@kernel.org" <shuah@kernel.org>,
"kevin.brodsky@arm.com" <kevin.brodsky@arm.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [External] : Re: [PATCH v2 Linux-6.12.y Linux-6.13.y 1/1] selftests/mm: build with -O2
Date: Tue, 11 Feb 2025 07:24:58 +0100 [thread overview]
Message-ID: <2025021143-limes-babble-e137@gregkh> (raw)
In-Reply-To: <C8A5840D-B312-40DC-A75D-3BA14614F8C4@oracle.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Mon, Feb 10, 2025 at 06:43:49PM +0000, Yifei Liu wrote:
> Hi Greg,
> Yes, looks we only need this for linux-6.12.y. Maybe we could use the v1 version which does not include the linux-6.13.y tag. Or I can send a v3 with the linux-6.12.y only.
As you know, we can't take patches for only older kernels and not newer
ones. Please submit them for all relevant branches, AND test your
patches before you submit them so that they don't fail on our side, as
that just wastes our energy :(
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-11 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 21:47 [PATCH v2 Linux-6.12.y Linux-6.13.y 1/1] selftests/mm: build with -O2 Yifei Liu
2025-02-05 12:14 ` Greg KH
2025-02-10 18:43 ` [External] : " Yifei Liu
2025-02-11 6:24 ` Greg KH [this message]
2025-02-12 0:33 ` Yifei Liu
2025-02-19 2:13 ` Yifei Liu
2025-02-19 5:09 ` Greg KH
2025-02-07 22:51 ` Sasha Levin
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=2025021143-limes-babble-e137@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yifei.l.liu@oracle.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