From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Kiko Piris <kernel@pirispons.net>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: 3.10.1 cpufreq suspend/resume regression still present in 3.10.2
Date: Mon, 22 Jul 2013 22:27:40 +0530 [thread overview]
Message-ID: <51ED6484.1070306@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130722165355.GA18371@kroah.com>
On 07/22/2013 10:23 PM, Greg KH wrote:
> On Mon, Jul 22, 2013 at 08:52:21PM +0530, Srivatsa S. Bhat wrote:
>> And both of them have been CC'ed to -stable. So they should be hitting
>> the stable tree soon.
>>
>> Hmm, that reminds me.. whenever a patch cc'ed to stable hit the mainline,
>> the patch signers used to receive an automatic email from Greg. I didn't
>> get that for the above two patches.. Did the process change due to the
>> recent discussions around -stable tree maintenance?
>
> No, it did not change, I just have 150+ pending patches for the
> 3.11-stable tree that I have yet to get through, give me a few weeks
> please.
>
Oh! Sure, no problem.
Thank you!
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2013-07-22 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 15:16 3.10.1 cpufreq suspend/resume regression still present in 3.10.2 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 [this message]
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
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=51ED6484.1070306@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pirispons.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--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.