linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [ACPI+PM] Changes for v3.11 merge window, no more new material for v3.11 (please)
Date: Thu, 27 Jun 2013 22:15:53 +0300	[thread overview]
Message-ID: <20130627191553.GB9294@intel.com> (raw)
In-Reply-To: <16355875.t52aFJBBuQ@vostro.rjw.lan>

On Thu, Jun 27, 2013 at 09:15:50PM +0200, Rafael J. Wysocki wrote:
> On Thursday, June 27, 2013 10:08:42 PM Mika Westerberg wrote:
> > On Thu, Jun 27, 2013 at 02:27:01PM +0200, Rafael J. Wysocki wrote:
> > > Hi All,
> > > 
> > > Below is a summary of my current queue for the v3.11 merge window.
> > > 
> > > I will be very reluctant to add anything that is not a fix for a serious
> > > problem to it from now on.  If you have such a fix, please let me know,
> > > however.
> > > 
> > > Other material will be queued up for 3.12, but I'd very much appreciate it
> > > if people refrained from sending me stuff which is not fixes until the
> > > release of 3.11-rc1.
> > 
> > I wonder what happened to the acpi_os_get_timer() patch?
> > 
> > https://patchwork.kernel.org/patch/2605021/
> 
> Well, I'm not sure to be honest.  I'll take it for 3.11.

Thanks!

      reply	other threads:[~2013-06-27 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 12:27 [ACPI+PM] Changes for v3.11 merge window, no more new material for v3.11 (please) Rafael J. Wysocki
2013-06-27 15:06 ` Viresh Kumar
2013-06-27 19:08 ` Mika Westerberg
2013-06-27 19:15   ` Rafael J. Wysocki
2013-06-27 19:15     ` Mika Westerberg [this message]

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=20130627191553.GB9294@intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --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 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).