From: Mark Rutland <mark.rutland@arm.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
linux-kernel@vger.kernel.org, frederic@kernel.org,
jstultz@google.com, juri.lelli@redhat.com, mingo@redhat.com,
peterz@infradead.org, tglx@linutronix.de,
vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH 4/5] sched: dynamic: Simplify irqentry_exit_cond_resched()
Date: Fri, 17 Jul 2026 14:57:21 +0100 [thread overview]
Message-ID: <alo0wRpn3neWEMnV@J2N7QTR9R3> (raw)
In-Reply-To: <2e141369-1b6f-425e-8648-a8969ee5d1b3@linux.ibm.com>
On Fri, Jul 17, 2026 at 07:19:03PM +0530, Shrikanth Hegde wrote:
> On 7/17/26 4:35 PM, Mark Rutland wrote:
> > On Mon, Jul 06, 2026 at 10:12:29AM +0530, Shrikanth Hegde wrote:
> > > JFYI,
> > > Christophe had sent this patch, I am sure you guys will sort out the
> > > conflicts. (I don't see it merged yet, but likely might)
> > >
> > > https://lore.kernel.org/all/2bf10a0afffefb6aca44bf2f864cc17471a80e31.1781870889.git.chleroy@kernel.org/
> >
> > Thanks for the heads-up!
> >
> > Sorry, I'd skipped Ccing all the arch folk as I hadn't expected anyone
> > was likely to be doing similar in the arch code right now. I'll make
> > sure you're both Cc'd for any subsequent versions.
> >
> > It looks like the only difference for powerpc is that I leave
> > need_irq_preemption() lying around. Christophe, if you're happy with
> > this series, I could pick a patch from you to remove that (e.g. take
> > your patch and apply it to the end of this series, reduced to removing
> > need_irq_preemption()).
> >
> > Any preference?
>
> I will go by Christophe preference.
>
> But i see it is in powerpc fixes branch and part of pull request.
> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes
>
> So, you might have to rebase on top of it.
Sorry, I didn't spot that. Thanks for the pointer!
I'll wait for that to land and rebase atop, then.
Mark.
next prev parent reply other threads:[~2026-07-17 13:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 13:33 [PATCH 0/5] sched: dynamic: Simplify PREEMPT_DYNAMIC Mark Rutland
2026-07-03 13:33 ` [PATCH 1/5] sched: dynamic: Make PREEMPT_DYNAMIC depend on ARCH_HAS_PREEMPT_LAZY Mark Rutland
2026-07-06 4:36 ` Shrikanth Hegde
2026-07-17 10:59 ` Mark Rutland
2026-07-27 12:37 ` Jinjie Ruan
2026-07-03 13:33 ` [PATCH 2/5] sched: dynamic: Simplify {cond,might}_resched() Mark Rutland
2026-07-06 4:59 ` Shrikanth Hegde
2026-07-17 11:03 ` Mark Rutland
2026-07-03 13:33 ` [PATCH 3/5] sched: dynamic: Simplify preempt_schedule{,_notrace}() Mark Rutland
2026-07-06 5:19 ` Shrikanth Hegde
2026-07-03 13:33 ` [PATCH 4/5] sched: dynamic: Simplify irqentry_exit_cond_resched() Mark Rutland
2026-07-06 4:42 ` Shrikanth Hegde
2026-07-17 11:05 ` Mark Rutland
2026-07-17 13:49 ` Shrikanth Hegde
2026-07-17 13:57 ` Mark Rutland [this message]
2026-07-27 11:28 ` Christophe Leroy (CS GROUP)
2026-07-03 13:33 ` [PATCH 5/5] sched: dynamic: Remove HAVE_PREEMPT_DYNAMIC_{CALL,KEY} Mark Rutland
2026-07-06 4:30 ` [PATCH 0/5] sched: dynamic: Simplify PREEMPT_DYNAMIC Shrikanth Hegde
2026-07-17 11:35 ` Mark Rutland
2026-07-30 15:39 ` Mete Durlu
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=alo0wRpn3neWEMnV@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=chleroy@kernel.org \
--cc=frederic@kernel.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®