public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: state of some x86 acpi patches
Date: Fri, 06 Feb 2009 19:18:45 -0800	[thread overview]
Message-ID: <498CFD95.5070004@kernel.org> (raw)
In-Reply-To: <498CF8DA.30004@goop.org>

Jeremy Fitzhardinge wrote:
> Yinghai Lu wrote:
>> Jeremy Fitzhardinge wrote:
>>  
>>> 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
>>>     
>>
>>
>> please check attached that are updated to today tip/master with ingo's
>> genapic patchset..
>>   
> 
> The look OK, but they didn't get merged into tip/master?
> 
Ingo is too busy...
It seems Len already agreed those patches can go through tip.

Ingo?

YH

       reply	other threads:[~2009-02-07  3:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4947FF4C.80706@goop.org>
     [not found] ` <20081216192534.GB843@elte.hu>
     [not found]   ` <alpine.LFD.2.00.0812311821110.3854@localhost.localdomain>
     [not found]     ` <495C677F.6080707@goop.org>
     [not found]       ` <20090102153957.GA1180@elte.hu>
     [not found]         ` <4980EE0C.4070308@goop.org>
     [not found]           ` <49810211.9030808@kernel.org>
     [not found]             ` <498CF8DA.30004@goop.org>
2009-02-07  3:18               ` Yinghai Lu [this message]
2009-02-08  0:09                 ` state of some x86 acpi patches 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

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=498CFD95.5070004@kernel.org \
    --to=yinghai@kernel.org \
    --cc=jeremy@goop.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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