Linux ACPI
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Yinghai Lu <yinghai@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: state of some x86 acpi patches
Date: Wed, 31 Dec 2008 18:38:15 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0812311821110.3854@localhost.localdomain> (raw)
In-Reply-To: <20081216192534.GB843@elte.hu>

On Tue, 16 Dec 2008, Ingo Molnar wrote:

> 
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> 
> > Hi Len,
> >
> > Have you seen these three patches?  Do they look OK to you?
> >
> > Yinghai Lu improve the third patch ("acpi: remove final __acpi_map_table 
> > mapping before setting acpi_gbl_permanent_mmap"), which I think Ingo 
> > sent you instead.
> 
> Len,
> 
> i asked about these patches before too - and if that's fine with you we'd 
> just queue them up in the x86 tree (like we did before the .28 merge 
> window). Most of the impact will be on x86. So an Acked-by from you would 
> be fine to start this.

Sorry for the delay.
I recall reading your e-mail on this and thought I replied to it,
but for some reason I found neither your original message nor
my reply when I searched my archives today.

But I did recall Ingo making a branch for this one, and so looking
at remotes/origin/acpi-for-len in ingo's tree...

It isn't immediately clear to me what problem this patch series solves,
and thus it is hard to judge how important this is.

It touches a lot of files, and it is going to run into a bunch of merge 
conflicts.

I'm not thrilled that the first part of the series makes changes
which are then undone by the later part of the series --
that doesn't help w/ conflict resolution...

The change to tbxface.c is an ACPICA API change.
It looks reasonable and it might be the right change,
but it is extra work -- we should sync with Bob
when he gets back from break.

So, this one is sort of a headache, how important is it?

thanks,
-- Len Brown, Intel Open Source Technology Center


  reply	other threads:[~2008-12-31 23:38 UTC|newest]

Thread overview: 15+ 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 [this message]
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
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
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=alpine.LFD.2.00.0812311821110.3854@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=jeremy@goop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox