public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 19 Feb 2025 06:09:07 +0100	[thread overview]
Message-ID: <2025021935-blandness-celibacy-5fea@gregkh> (raw)
In-Reply-To: <4FF4FFA8-1385-452D-9B44-D791B664D4E8@oracle.com>

On Wed, Feb 19, 2025 at 02:13:29AM +0000, Yifei Liu wrote:
> 
> 
> > On Feb 11, 2025, at 4:33 PM, Yifei Liu <yifei.l.liu@oracle.com> wrote:
> > 
> > 
> > 
> >> On Feb 10, 2025, at 10:24 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> 
> >> A: https://urldefense.com/v3/__http://en.wikipedia.org/wiki/Top_post__;!!ACWV5N9M2RV99hQ!I6O0EcBYMun5zy7pK39ZG9aJYrbv3Uy7IaJYl-fKOXJfmImBbzfXDFfOWeYY2o1JutHPBoAoI_b7xJQyjQ5nnfgv$ 
> >> 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?
> >> 
> > Hi Greg,
> > Sorry for the top-posting. I will not do that any more. 
> >> https://urldefense.com/v3/__http://daringfireball.net/2007/07/on_top__;!!ACWV5N9M2RV99hQ!I6O0EcBYMun5zy7pK39ZG9aJYrbv3Uy7IaJYl-fKOXJfmImBbzfXDFfOWeYY2o1JutHPBoAoI_b7xJQyjanSNOhz$
> >> 
> >> 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 :(
> > For this patch, I believe it failed to apply to linux-6.13 due to another same patch applied before it. Commit d9eb5a1e76f5 ("selftests/mm: build with -O2”) goes into linux-6.13 with tag v6.13.2, last week’s tag. I checked the queue-6.12 and do not see this patch yet for v6.12. I think we still need this for v6.12. About the patch, it fixes a build issue for selftest/mm, which is bacported to v6.12. Thus this patch should only be backported to v6.12.
> > 
> > I tested it on my device and it works fine and solved the failure of selftest.
> > 
> Hi Greg, 
> 
> I checked the v6.12.16 tag released last Friday. It does not contain this patch. It looks we will not see the same situation we have for v6.13 like I mentioned above and it’s safe to include this in v6.12. 

I don't know what "this patch" is here, sorry, I have no context.

> I could resend a v3 with all the linux-6.13.y tags removed if you want. 

Whatever needs to be applied, yes, please resend it properly.

thanks,

greg k-h

  reply	other threads:[~2025-02-19  5:09 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
2025-02-12  0:33       ` Yifei Liu
2025-02-19  2:13         ` Yifei Liu
2025-02-19  5:09           ` Greg KH [this message]
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=2025021935-blandness-celibacy-5fea@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