public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: ACPI patch process problems again
Date: Sat, 10 Jun 2006 23:29:01 +0200	[thread overview]
Message-ID: <448B399D.7040703@free.fr> (raw)
In-Reply-To: <20060610211156.GT1651@parisc-linux.org>

Hi,

Matthew Wilcox wrote:
> On Sat, Jun 10, 2006 at 10:51:13PM +0200, Matthieu CASTET wrote:
> 
>>Le Sat, 10 Jun 2006 10:41:50 -0600, Matthew Wilcox a ?crit?:
>>
>>>ACPI ADDRESSn resources can describe both memory and port io, but the
>>>current code assumes they're descibing memory, which isn't true for HP's
>>>ia64 systems.
>>>
>>
>>There already a patch for that in -mm kernel
> 
> 
> Yes, the original author just contacted me to tell me.  It seems to me
> that we have a process problem when a bug gets fixed on March 28th,
> but not propagated upstream by June 10th.  That's almost 11 weeks,
> and I'm sure it'll be more by the time it's finally merged.  I thought
> the days of ACPI process problems were behind us ;-(

The problem is that this patch (and your patch) introduce a regression 
for some boxes.

See http://bugzilla.kernel.org/show_bug.cgi?id=6292 for more info.

I submited today a fix for this regression.

Matthieu

      reply	other threads:[~2006-06-10 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 16:41 [PATCH] pnpacpi mishandles port io ADDRESS resources Matthew Wilcox
2006-06-10 20:51 ` Matthieu CASTET
2006-06-10 21:11   ` ACPI patch process problems again Matthew Wilcox
2006-06-10 21:29     ` matthieu castet [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=448B399D.7040703@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=torvalds@osdl.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