public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
	NXP Linux Team <Linux-imx@nxp.com>
Subject: Re: cpuidle regression ?
Date: Tue, 10 Dec 2019 09:06:19 +0100	[thread overview]
Message-ID: <ce4b6bb4-7921-598d-b7f1-1bc377e07602@linaro.org> (raw)
In-Reply-To: <c326a33d-f147-b6c2-a967-1170cf6917a3@linaro.org>

On 09/12/2019 18:22, Daniel Lezcano wrote:

[ ... ]

> However, kernelci does no longer report a regression on the baseline
> with your patch applied on my 'testing' branch.
> 
> I can not guarantee the bug is fixed because I can't reproduce it
> locally and check the patch is effectively solving the issue.
> 
> In order to increase the confidence on the fix, I updated the branch
> without your patch, so in a few hours, we should see the if the
> regression appears or not.

The regression came back without the patch.


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2019-12-10  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08 10:39 cpuidle regression ? Daniel Lezcano
2019-12-09  9:26 ` Rafael J. Wysocki
2019-12-09 10:32   ` Daniel Lezcano
2019-12-09 10:50     ` Rafael J. Wysocki
2019-12-09 11:35       ` Daniel Lezcano
2019-12-09 11:55         ` Rafael J. Wysocki
2019-12-09 17:22           ` Daniel Lezcano
2019-12-10  8:06             ` Daniel Lezcano [this message]
2019-12-10  8:07               ` Rafael J. Wysocki
2019-12-10 11:48 ` [PATCH] cpuidle: Fix cpuidle_driver_state_disabled() Rafael J. Wysocki

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=ce4b6bb4-7921-598d-b7f1-1bc377e07602@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Linux-imx@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.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