Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Waiman Long <longman@redhat.com>
Cc: stable@vger.kernel.org, "Tejun Heo" <tj@kernel.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Giuseppe Scrivano" <gscrivan@redhat.com>
Subject: Re: [PATCH 5.15 1/3] cgroup/cpuset: Skip spread flags update on v2
Date: Wed, 19 Apr 2023 09:20:22 +0200	[thread overview]
Message-ID: <2023041902-giddily-obliged-32ce@gregkh> (raw)
In-Reply-To: <20230417153647.3374211-1-longman@redhat.com>

On Mon, Apr 17, 2023 at 11:36:45AM -0400, Waiman Long wrote:
> commit 18f9a4d47527772515ad6cbdac796422566e6440 upstream.
> 
> Cpuset v2 has no spread flags to set. So we can skip spread
> flags update if cpuset v2 is being used. Also change the name to
> cpuset_update_task_spread_flags() to indicate that there are multiple
> spread flags.
> 
> Signed-off-by: Waiman Long <longman@redhat.com>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
>  kernel/cgroup/cpuset.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 

Same as the 5.10.y series, I've dropped all of these due to build
errors.

thanks,

greg k-h

      parent reply	other threads:[~2023-04-19  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 15:36 [PATCH 5.15 1/3] cgroup/cpuset: Skip spread flags update on v2 Waiman Long
2023-04-17 15:36 ` [PATCH 5.15 2/3] cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly Waiman Long
2023-04-17 15:36 ` [PATCH 5.15 3/3] cgroup/cpuset: Add cpuset_can_fork() and cpuset_cancel_fork() methods Waiman Long
2023-04-19  7:20 ` Greg Kroah-Hartman [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=2023041902-giddily-obliged-32ce@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=gscrivan@redhat.com \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=tj@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