The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: torvalds@linux-foundation.org
Cc: void@manifault.com, mingo@redhat.com, peterz@infradead.org,
	tglx@linutronix.de, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCHSET sched_ext/for-6.11] sched_ext: Clean up kernel/sched/ext.h
Date: Mon, 8 Jul 2024 09:39:32 -1000	[thread overview]
Message-ID: <ZoxAdMLsfMJYVtj8@slm.duckdns.org> (raw)
In-Reply-To: <20240623015057.3383223-1-tj@kernel.org>

On Sat, Jun 22, 2024 at 03:50:19PM -1000, Tejun Heo wrote:
> Hello,
> 
> While sched_ext was out of tree, kernel/sched/ext.h contained declarations
> and definitions which aren't ideal but are helpful for forward porting. This
> patchset cleans them up.
> 
> - for_balance_class_range() is removed and instead open coded in
>   put_prev_task_balance().
> 
> - Some declarations and definitions in kernel/sched/ext.h are moved to
>   kernel/sched/sched.h.
> 
> This patchset contains the following three patches:
> 
>   0001-sched_ext-Minor-cleanups-in-kernel-sched-ext.h.patch
>   0002-sched-sched_ext-Open-code-for_balance_class_range.patch
>   0003-sched-sched_ext-Move-some-declarations-from-kernel-s.patch

Applied to sched_ext/for-6.11.

Thanks.

-- 
tejun

      parent reply	other threads:[~2024-07-08 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23  1:50 [PATCHSET sched_ext/for-6.11] sched_ext: Clean up kernel/sched/ext.h Tejun Heo
2024-06-23  1:50 ` [PATCH 1/3] sched_ext: Minor cleanups in kernel/sched/ext.h Tejun Heo
2024-06-23  7:16   ` David Vernet
2024-06-23  1:50 ` [PATCH 2/3] sched, sched_ext: Open code for_balance_class_range() Tejun Heo
2024-06-23  7:17   ` David Vernet
2024-06-23  1:50 ` [PATCH 3/3] sched, sched_ext: Move some declarations from kernel/sched/ext.h to sched.h Tejun Heo
2024-06-23  7:48   ` David Vernet
2024-07-08 19:39 ` Tejun Heo [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=ZoxAdMLsfMJYVtj8@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=void@manifault.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