From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Gautham R Shenoy <ego@linux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@linux.ibm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, joedecke@de.ibm.com,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards
Date: Wed, 28 Apr 2021 17:04:48 +0530 [thread overview]
Message-ID: <20210428113447.GA24644@in.ibm.com> (raw)
In-Reply-To: <20210428080326.GL6564@kitsune.suse.cz>
Hello Michal,
On Wed, Apr 28, 2021 at 10:03:26AM +0200, Michal Suchánek wrote:
> >
> That's a nice detailed explanation. Maybe you could summarize it in the
> commit message so that people looking at the patch in the future can
> tell where the value comes from.
Sure, I will do that and send a v2 with the updated commit message.
>
> Thanks
>
> Michal
WARNING: multiple messages have this Message-ID (diff)
From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Gautham R Shenoy <ego@linux.vnet.ibm.com>,
linux-pm@vger.kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
joedecke@de.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards
Date: Wed, 28 Apr 2021 17:04:48 +0530 [thread overview]
Message-ID: <20210428113447.GA24644@in.ibm.com> (raw)
In-Reply-To: <20210428080326.GL6564@kitsune.suse.cz>
Hello Michal,
On Wed, Apr 28, 2021 at 10:03:26AM +0200, Michal Suchánek wrote:
> >
> That's a nice detailed explanation. Maybe you could summarize it in the
> commit message so that people looking at the patch in the future can
> tell where the value comes from.
Sure, I will do that and send a v2 with the updated commit message.
>
> Thanks
>
> Michal
next prev parent reply other threads:[~2021-04-28 11:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 15:07 [PATCH] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards Gautham R. Shenoy
2021-04-22 15:07 ` Gautham R. Shenoy
2021-04-22 17:57 ` Vaidyanathan Srinivasan
2021-04-22 17:57 ` Vaidyanathan Srinivasan
2021-04-23 7:35 ` Michal Suchánek
2021-04-23 7:35 ` Michal Suchánek
2021-04-23 15:59 ` Vaidyanathan Srinivasan
2021-04-23 15:59 ` Vaidyanathan Srinivasan
2021-04-23 17:45 ` Michal Suchánek
2021-04-23 17:45 ` Michal Suchánek
2021-04-23 18:29 ` Vaidyanathan Srinivasan
2021-04-23 18:29 ` Vaidyanathan Srinivasan
2021-04-23 18:42 ` Michal Suchánek
2021-04-23 18:42 ` Michal Suchánek
2021-04-24 7:37 ` Vaidyanathan Srinivasan
2021-04-24 7:37 ` Vaidyanathan Srinivasan
2021-04-25 11:07 ` Michal Suchánek
2021-04-25 11:07 ` Michal Suchánek
2021-04-28 5:58 ` Gautham R Shenoy
2021-04-28 5:58 ` Gautham R Shenoy
2021-04-28 8:03 ` Michal Suchánek
2021-04-28 8:03 ` Michal Suchánek
2021-04-28 11:34 ` Gautham R Shenoy [this message]
2021-04-28 11:34 ` Gautham R Shenoy
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=20210428113447.GA24644@in.ibm.com \
--to=ego@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=daniel.lezcano@linaro.org \
--cc=joedecke@de.ibm.com \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=rjw@rjwysocki.net \
--cc=svaidy@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.