From: Christian Loehle <christian.loehle@arm.com>
To: linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@redhat.com
Cc: juri.lelli@redhat.com, dietmar.eggemann@arm.com,
vincent.guittot@linaro.org
Subject: Re: [PATCH v2 0/2] sched/topology: Fix sched_is_eas_possible() prints
Date: Wed, 2 Apr 2025 15:09:31 +0100 [thread overview]
Message-ID: <24180e03-b608-4fb0-9215-b2bf1ea22bf0@arm.com> (raw)
In-Reply-To: <20250319131324.224228-1-christian.loehle@arm.com>
On 3/19/25 13:13, Christian Loehle wrote:
> Fix two EAS abort condition prints by adding the missing newline
>
> v2:
> Split series for backports, Cc stable and add fixes tags.
>
> Christian Loehle (2):
> sched/topology: Fix EAS cpufreq check print
> sched/topology: Fix EAS freq-invariance print
>
> kernel/sched/topology.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.34.1
>
Peter, Ingo,
Could someone pick these up pretty please?
prev parent reply other threads:[~2025-04-02 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 13:13 Christian Loehle
2025-03-19 13:13 ` [PATCH v2 1/2] sched/topology: Fix EAS cpufreq check print Christian Loehle
2025-03-19 13:13 ` [PATCH v2 2/2] sched/topology: Fix EAS freq-invariance print Christian Loehle
2025-04-02 14:09 ` Christian Loehle [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=24180e03-b608-4fb0-9215-b2bf1ea22bf0@arm.com \
--to=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®