All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<dietmar.eggemann@arm.com>,
	<linux-arm-kernel@lists.infradead.org>, <sudeep.holla@arm.com>,
	<cristian.marussi@arm.com>, <linux-samsung-soc@vger.kernel.org>,
	<rafael@kernel.org>, <viresh.kumar@linaro.org>,
	<quic_sibis@quicinc.com>
Subject: Re: [PATCH 0/2] Update Energy Model with perfromance limits
Date: Fri, 5 Apr 2024 10:56:00 +0100	[thread overview]
Message-ID: <20240405105600.000019fd@Huawei.com> (raw)
In-Reply-To: <20240403162315.1458337-1-lukasz.luba@arm.com>

On Wed,  3 Apr 2024 17:23:13 +0100
Lukasz Luba <lukasz.luba@arm.com> wrote:

Typo in patch title.  performance

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<dietmar.eggemann@arm.com>,
	<linux-arm-kernel@lists.infradead.org>, <sudeep.holla@arm.com>,
	<cristian.marussi@arm.com>, <linux-samsung-soc@vger.kernel.org>,
	<rafael@kernel.org>, <viresh.kumar@linaro.org>,
	<quic_sibis@quicinc.com>
Subject: Re: [PATCH 0/2] Update Energy Model with perfromance limits
Date: Fri, 5 Apr 2024 10:56:00 +0100	[thread overview]
Message-ID: <20240405105600.000019fd@Huawei.com> (raw)
In-Reply-To: <20240403162315.1458337-1-lukasz.luba@arm.com>

On Wed,  3 Apr 2024 17:23:13 +0100
Lukasz Luba <lukasz.luba@arm.com> wrote:

Typo in patch title.  performance

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-04-05  9:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 16:23 [PATCH 0/2] Update Energy Model with perfromance limits Lukasz Luba
2024-04-03 16:23 ` Lukasz Luba
2024-04-03 16:23 ` [PATCH 1/2] PM: EM: Add min/max available performance state limits Lukasz Luba
2024-04-03 16:23   ` Lukasz Luba
2024-04-09 14:47   ` Hongyan Xia
2024-04-09 14:47     ` Hongyan Xia
2024-04-22  7:24     ` Lukasz Luba
2024-04-22  7:24       ` Lukasz Luba
2024-04-22  7:46   ` Dietmar Eggemann
2024-04-22  7:46     ` Dietmar Eggemann
2024-04-03 16:23 ` [PATCH 2/2] cpufreq: scmi: Update Energy Model with allowed performance limits Lukasz Luba
2024-04-03 16:23   ` Lukasz Luba
2024-04-22 13:11   ` Dietmar Eggemann
2024-04-22 13:11     ` Dietmar Eggemann
2024-04-22 13:55     ` Lukasz Luba
2024-04-22 13:55       ` Lukasz Luba
2024-05-01  9:26   ` Cristian Marussi
2024-05-01  9:26     ` Cristian Marussi
2024-04-05  9:56 ` Jonathan Cameron [this message]
2024-04-05  9:56   ` [PATCH 0/2] Update Energy Model with perfromance limits Jonathan Cameron
2024-04-05 10:11   ` Lukasz Luba
2024-04-05 10:11     ` Lukasz Luba

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=20240405105600.000019fd@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=cristian.marussi@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=quic_sibis@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@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 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.