linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: dirk.j.brandewie@intel.com,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] intel_pstate updates for v3.14-rcX
Date: Wed, 19 Feb 2014 10:26:52 -0800	[thread overview]
Message-ID: <5304F76C.1070500@intel.com> (raw)
In-Reply-To: <2254366.ixXkMqbYNC@vostro.rjw.lan>

On 02/18/2014 04:53 PM, Rafael J. Wysocki wrote:
> On Tuesday, February 18, 2014 04:35:26 PM Dirk Brandewie wrote:
>> On 02/18/2014 04:43 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, February 18, 2014 04:24:02 PM Dirk Brandewie wrote:
>>>> On Tuesday, February 18, 2014, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>>>>
>>>>> On Tuesday, February 18, 2014 03:53:48 PM Dirk Brandewie wrote:
>>>>>> On 02/18/2014 02:27 PM, Rafael J. Wysocki wrote:
>>>>>>> On Tuesday, February 18, 2014 12:29:54 PM Dirk Brandewie wrote:
>>>>>>>> Hi Rafael,
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>> On 02/12/2014 10:01 AM, dirk.brandewie@gmail.com <javascript:;>wrote:
>>>>>>>>> From: Dirk Brandewie <dirk.j.brandewie@intel.com <javascript:;>>
>>>>>>>>>
>>>>>>>>> Based on v3.14-rc2
>>>>>>>>>
>>>>>>>>> Patch 1 removes energy reporting the patch from Maurizio Lambardi
>>>>>>>>>      intel_pstate: fix race condition in intel_pstate_init() can be
>>>>> dropped.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Any reason why patches 2-5 did not make rc3 other than timing?
>>>>>>>>
>>>>>>>> Patches 2/3 can easily wait for v3.15.x
>>>>>>>>
>>>>>>>> Patches 4/5 fix bugs that are in the wild.
>>>>>>>
>>>>>>> I asked you about them, but you didn't reply:
>>>>>>>
>>>>>>> http://marc.info/?l=linux-pm&m=139225158531023&w=4
>>>>>>>
>>>>>>> Again, do patches [4-5/5] depend on [2-3/5]?
>>>>>>>
>>>>>>> If not, I can queue them up for -rc4.
>>>>>>
>>>>>> All the patches are independent of one another.
>>>>>>
>>>>>> Patch 2 is straight cleanup no functional change but reduces the memory
>>>>>> footprint slightly.
>>>>>>
>>>>>> Patch 3 is a bug that will only be seen when the PID is reset at init
>>>>> time
>>>>>> or when a change is made to PID params via debugfs.  The problem will
>>>>> only
>>>>>> exist for one sample time since it is setting last_err in the PID.
>>>>>>
>>>>>> Patch 4-5 are bugs found during Baytrail-T testing
>>>>>
>>>>> Are there any pointers to bug reports that may be included in the
>>>>> changelogs
>>>>> of these?
>>>>
>>>>
>>>> No.  I got the reports via email.  I could probably get the reporters to
>>>> file bugzillas.
>>>
>>> It would be good to add information about what machines are affected
>>> and what the user-visible problems are to the changelogs for future
>>> reference.
>>>
>>> And do we want these two patches in -stable?  If so, what -stable series should
>>> they go into?
>>
>> Patch 2 v3.10+
>>
>> Patch 3 v3.12+
>
> You said [2-3/5] were cleanups, so why do you think they are -stable material?

I misspoke these are not stable material

>
>> Patch 4/5 v3.13+
>
> OK
>
> What about the bug information?  Can you please point me to the e-mail threads
> where the bugs were discussed at least?
>
> Rafael
>


  reply	other threads:[~2014-02-19 18:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 18:01 [PATCH 0/5] intel_pstate updates for v3.14-rcX dirk.brandewie
2014-02-12 18:01 ` [PATCH 1/5] intel_pstate: Remove energy reporting from pstate_sample tracepoint dirk.brandewie
2014-02-12 18:01 ` [PATCH 2/5] intel_pstate: remove unneeded sample buffers dirk.brandewie
2014-02-13  0:42   ` Li, Aubrey
2014-02-12 18:01 ` [PATCH 3/5] intel_pstate: fix pid_reset to use fixed point values dirk.brandewie
2014-02-12 18:01 ` [PATCH 4/5] intel_pstate: Use LFM bus ratio as min ratio/P state dirk.brandewie
2014-02-19  0:58   ` Rafael J. Wysocki
2014-02-19 18:35     ` [PATCH v2] " dirk.brandewie
2014-02-20  0:44       ` Rafael J. Wysocki
2014-02-12 18:01 ` [PATCH 5/5] intel_pstate: Add support for Baytrail turbo P states dirk.brandewie
2014-02-13  0:47 ` [PATCH 0/5] intel_pstate updates for v3.14-rcX Rafael J. Wysocki
2014-02-13  1:00   ` Rafael J. Wysocki
2014-02-13  1:23     ` Rafael J. Wysocki
2014-02-18 20:29 ` Dirk Brandewie
2014-02-18 22:27   ` Rafael J. Wysocki
2014-02-18 23:53     ` Dirk Brandewie
2014-02-19  0:34       ` Rafael J. Wysocki
     [not found]         ` <CANOOhLToR8ajjiM1x7m_4Pbak3sUkjfq0h4EX6dz1U23D3X3EA@mail.gmail.com>
2014-02-19  0:43           ` Rafael J. Wysocki
2014-02-19  0:35             ` Dirk Brandewie
2014-02-19  0:53               ` Rafael J. Wysocki
2014-02-19 18:26                 ` Dirk Brandewie [this message]
2014-02-20  0:43                   ` 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=5304F76C.1070500@intel.com \
    --to=dirk.brandewie@gmail.com \
    --cc=dirk.j.brandewie@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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;
as well as URLs for NNTP newsgroup(s).