public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: wujing <realwujing@qq.com>
Cc: dongml2@chinatelecom.cn, linux-kernel@vger.kernel.org,
	menglong8.dong@gmail.com, mingo@redhat.com, peterz@infradead.org,
	stable@vger.kernel.org, yuanql9@chinatelecom.cn
Subject: Re: Re: [PATCH] sched/fair: Correct CPU selection from isolated domain
Date: Tue, 30 Jul 2024 11:51:46 +0200	[thread overview]
Message-ID: <2024073011-operating-pointless-7ab9@gregkh> (raw)
In-Reply-To: <tencent_02C238CCB4CAA1D0C58AF9A89E8263AE740A@qq.com>

On Tue, Jul 30, 2024 at 05:40:17PM +0800, wujing wrote:
> > What "current patch"?
> >
> > confused,
> >
> > greg k-h
> 
> The current patch is in my first email.

What message exactly?  I don't see any such message on the stable list.

> Please ignore the previous two emails.
> The "current patch" mentioned in the earlier emails refers to the upstream
> status, but the latest upstream patch can no longer be applied to linux-4.19.y.

Again, please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

thanks,

greg k-h

  reply	other threads:[~2024-07-30  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  7:10 [PATCH] sched/fair: Correct CPU selection from isolated domain wujing
2024-07-30  8:22 ` Peter Zijlstra
2024-07-30  9:03   ` wujing
2024-07-30  9:11     ` Greg KH
2024-07-30  9:25       ` wujing
2024-07-30  9:30       ` wujing
2024-07-30  9:41         ` Greg KH
2024-07-30  9:40       ` wujing
2024-07-30  9:51         ` Greg KH [this message]
2024-07-30 10:11           ` wujing
2024-07-30 10:20             ` Greg KH
2024-07-30  9:02 ` zhengzucheng

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=2024073011-operating-pointless-7ab9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dongml2@chinatelecom.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menglong8.dong@gmail.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=realwujing@qq.com \
    --cc=stable@vger.kernel.org \
    --cc=yuanql9@chinatelecom.cn \
    /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