From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: christian.loehle@arm.com
Cc: dietmar.eggemann@arm.com, elif.topuz@arm.com,
kayracizmeci@gmail.com, kprateek.nayak@amd.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, sh@gentwo.org, vincent.guittot@linaro.org
Subject: Re: [PATCH v2 4/5] sched/eevdf: Keep expired protection expired across reweighting
Date: Fri, 2 Oct 2026 17:57:29 +0300 [thread overview]
Message-ID: <20261002145729.11981-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <ac4671ff-18a7-4447-84e6-30d35df1c7af@arm.com>
> No, you're correct, do you wanna fold mine into your fix and send that out?
> (I think it looks better squashed but feel free to just pick mine up as your 1/2
> if you disagree)
> With 1/5 and 3+5/5 dropped there's only the refactor remaining and I might
> as well send that as standalone.
OK, I'll squash it, do some magic and send it afterwards. Something unexpected happens,
I'll mail here. I'll add your Co-developed-by and Signed-off-by, hope that's OK.
Thanks,
Kayra :>
next prev parent reply other threads:[~2026-10-02 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:40 [PATCH v2 0/5] sched/eevdf: Keep slice protection boundaries consistent Christian Loehle
2026-10-01 13:40 ` [PATCH v2 1/5] sched/fair: Take slice protection into account when arming HRTICK Christian Loehle
2026-10-01 13:43 ` Peter Zijlstra
2026-10-01 14:01 ` Christian Loehle
2026-10-01 13:40 ` [PATCH v2 2/5] sched/eevdf: Share the slice protection calculation Christian Loehle
2026-10-01 13:40 ` [PATCH v2 3/5] sched/eevdf: Cap protection when current has the shortest slice Christian Loehle
2026-10-01 13:55 ` Peter Zijlstra
2026-10-01 13:57 ` Christian Loehle
2026-10-01 13:40 ` [PATCH v2 4/5] sched/eevdf: Keep expired protection expired across reweighting Christian Loehle
2026-10-01 16:46 ` Kayra Cizmeci
2026-10-01 21:51 ` Christian Loehle
2026-10-02 14:57 ` Kayra Cizmeci [this message]
2026-10-01 13:40 ` [PATCH v2 5/5] sched/eevdf: Update protection after restoring current Christian Loehle
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=20261002145729.11981-1-kayracizmeci@gmail.com \
--to=kayracizmeci@gmail.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=elif.topuz@arm.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sh@gentwo.org \
--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
all inboxes | Powered by JetHome®