All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Len Brown <lenb@kernel.org>, Yinghai Lu <yinghai@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: state of some x86 acpi patches
Date: Wed, 28 Jan 2009 15:45:16 -0800	[thread overview]
Message-ID: <4980EE0C.4070308@goop.org> (raw)
In-Reply-To: <20090102153957.GA1180@elte.hu>

Ingo Molnar wrote:
> yes, that end result is the desired state of things. We did run with this 
> for several months and resolved all the cases that needed fixing, but 
> dropped them when the ACPI tree moved out from under us.
>
> Can resurrect it if Len feels OK about the concept. Len, you shouldnt 
> worry about conflicts - we can do it after the ACPI changes of this merge 
> window are upstream so there should be no conflict trouble at all. How 
> does that sound?
>   

Doesn't look like these changes made it in this time.  Did they get 
overlooked, or did some other problem come up?  Or did you want me to 
dig them up?

Thanks,
    J

  parent reply	other threads:[~2009-01-28 23:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 19:19 state of some x86 acpi patches Jeremy Fitzhardinge
2008-12-16 19:25 ` Ingo Molnar
2008-12-31 23:38   ` Len Brown
2009-01-01  6:49     ` Jeremy Fitzhardinge
2009-01-02 15:39       ` Ingo Molnar
2009-01-02 22:28         ` Len Brown
2009-01-28 23:45         ` Jeremy Fitzhardinge [this message]
2009-01-29  1:10           ` Yinghai Lu
2009-02-07  2:58             ` Jeremy Fitzhardinge
2009-02-07  3:18               ` Yinghai Lu
2009-02-08  0:09                 ` Jeremy Fitzhardinge
2009-02-09 12:37                   ` Ingo Molnar
2009-02-15 19:36                     ` Ingo Molnar
2009-02-15 22:06                       ` Yinghai Lu
2009-02-15 22:25                         ` Ingo Molnar
2009-02-15 22:46                         ` Ingo Molnar
2009-02-15 23:10                           ` Yinghai Lu
2009-02-20 21:54                             ` Tony Luck
2009-02-20 21:55                               ` Yinghai Lu
2008-12-18 13:44 ` Andi Kleen
2008-12-18 19:46   ` Jeremy Fitzhardinge
2008-12-18 21:47     ` Ingo Molnar

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=4980EE0C.4070308@goop.org \
    --to=jeremy@goop.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yinghai@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 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.