public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: peterz@infradead.org, mingo@redhat.com,
	vincent.guittot@linaro.org, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, dietmar.eggemann@arm.com, nico@fluxnic.net
Subject: Re: [PATCH 0/2] sched/deadline: minor code cleanups
Date: Wed, 15 Oct 2025 10:41:48 +0200	[thread overview]
Message-ID: <aO9eTCDQDqDDbj0B@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <20251014100342.978936-1-sshegde@linux.ibm.com>

Hello,

On 14/10/25 15:33, Shrikanth Hegde wrote:
> While trying to understand the dl_server changes, noticed these minor
> code optimizations/cleanups possible. 
> 
> Let me know if these should be squashed into one patch. Kept is separate
> as of now.
> 
> No change in functionality. Could save a few cycles.
> 
> Shrikanth Hegde (2):
>   sched/deadline: minor code cleanups
>   sched/deadline: Use cpumask_weight_and in dl_bw_cpus

For the series (I would keep the fixes separate)

Acked-by: Juri Lelli <juri.lelli@redhat.com>

Thanks,
Juri


  parent reply	other threads:[~2025-10-15  8:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 10:03 [PATCH 0/2] sched/deadline: minor code cleanups Shrikanth Hegde
2025-10-14 10:03 ` [PATCH 1/2] " Shrikanth Hegde
2025-11-10 14:10   ` Peter Zijlstra
2025-11-10 14:17     ` Peter Zijlstra
2025-11-11 11:37   ` [tip: sched/core] sched/deadline: Minor cleanup in select_task_rq_dl() tip-bot2 for Shrikanth Hegde
2025-11-11 16:33   ` tip-bot2 for Shrikanth Hegde
2025-10-14 10:03 ` [PATCH 2/2] sched/deadline: Use cpumask_weight_and in dl_bw_cpus Shrikanth Hegde
2025-11-10 14:11   ` Peter Zijlstra
2025-11-11 11:37   ` [tip: sched/core] sched/deadline: Use cpumask_weight_and() " tip-bot2 for Shrikanth Hegde
2025-11-11 16:33   ` tip-bot2 for Shrikanth Hegde
2025-10-15  8:41 ` Juri Lelli [this message]
2025-11-10  8:25   ` [PATCH 0/2] sched/deadline: minor code cleanups Shrikanth Hegde

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=aO9eTCDQDqDDbj0B@jlelli-thinkpadt14gen4.remote.csb \
    --to=juri.lelli@redhat.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nico@fluxnic.net \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sshegde@linux.ibm.com \
    --cc=vincent.guittot@linaro.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