From: Paul Bolle <pebolle@tiscali.nl>
To: Kiko Piris <kernel@pirispons.net>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: 3.10.1 cpufreq suspend/resume regression still present in 3.10.2
Date: Mon, 22 Jul 2013 18:12:29 +0200 [thread overview]
Message-ID: <1374509549.15242.31.camel@x61.thuisdomein> (raw)
In-Reply-To: <51ED56FF.9030508@linux.vnet.ibm.com>
Kiko,
On Mon, 2013-07-22 at 21:29 +0530, Srivatsa S. Bhat wrote:
> On 07/22/2013 09:24 PM, Kiko Piris wrote:
> > I saw your message and was going to apply it, but I didn’t fully
> > understand that thread and wasn’t sure exactly what patch I was supposed
> > to try and above what version should I apply it (my “kernel skills” are
> > very very limited).
Perhaps my message was unclear, too terse, whatever. I wouldn't have
minded to clarify my message (ie, "apply path x on top of release y).
> > If you want me to test any patch, I would be more than happy to do so; I
> > would be grafeful if you told me exactly what patch to apply and above
> > which kernel version.
>
> Try applying the two mainline commits that I mentioned in my previous
> mail, on top of 3.10.2 and check if it fixes your problem.
Please try what Srivatsa suggested, as Srivatsa understands this issue
much better than I do!
Paul Bolle
next prev parent reply other threads:[~2013-07-22 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 15:16 Kiko Piris
2013-07-22 15:22 ` Srivatsa S. Bhat
2013-07-22 16:53 ` Greg KH
2013-07-22 16:57 ` Srivatsa S. Bhat
2013-07-22 15:34 ` Paul Bolle
2013-07-22 15:54 ` Kiko Piris
2013-07-22 15:59 ` Srivatsa S. Bhat
2013-07-22 16:12 ` Paul Bolle [this message]
2013-07-22 16:38 ` Srivatsa S. Bhat
2013-07-22 17:05 ` Kiko Piris
2013-07-22 20:52 ` Kiko Piris
2013-07-23 8:16 ` Srivatsa S. Bhat
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=1374509549.15242.31.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pirispons.net \
--cc=linux-kernel@vger.kernel.org \
--cc=srivatsa.bhat@linux.vnet.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 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®