public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Adam Belay <ambx1@neo.rr.com>
Cc: Andrew Morton <akpm@osdl.org>, "Brown, Len" <len.brown@intel.com>,
	linux-acpi@vger.kernel.org, castet.matthieu@free.fr,
	bjorn.helgaas@hp.com, uwe.bugla@gmx.de
Subject: Re: [patch 11/18] pnpacpi: reject ACPI_PRODUCER resources
Date: Tue, 27 Jun 2006 15:29:50 +0800	[thread overview]
Message-ID: <1151393390.21189.59.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20060627073704.GD3438@neo.rr.com>

On Tue, 2006-06-27 at 15:37 +0800, Adam Belay wrote:
> On Tue, Jun 27, 2006 at 12:03:24AM -0700, Andrew Morton wrote: 
> > On Tue, 27 Jun 2006 02:30:13 -0400 
> > "Brown, Len" <len.brown@intel.com> wrote: 
> >  
> > > NAK, per Shaohua's comments in the bug report.  
> > >  
> > > ... 
> > > 
> > > > 
> > > >This patch fixes bug 6292  
> > > >(http://bugzilla.kernel.org/show_bug.cgi?id=6292). 
> >  
> > Sigh.  Uwe is available to test patches, should any happen to get
> written.
> 
> I think we want something like this one...
> 
> http://bugzilla.kernel.org/attachment.cgi?id=7931&action=view
Exactly.

> Regarding the bug report: Shaohua, if I understand correctly, we used
> to 
> blacklist PCI root buses in the old implementation but it was changed
> here:
> 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c4bb6f5ad968540d7f9619565bacd18d7419b85f
Thanks and sorry I didn't find the issue before. We'd better blacklist
root bridge. I saw at lest one BIOS (IA64 box) didn't assign correct
producer/consumer flag to root bridge resources. Blacklist it is much
safer.

Thanks,
Shaohua

  reply	other threads:[~2006-06-27  7:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27  6:30 [patch 11/18] pnpacpi: reject ACPI_PRODUCER resources Brown, Len
2006-06-27  7:03 ` Andrew Morton
2006-06-27  7:37   ` Adam Belay
2006-06-27  7:29     ` Shaohua Li [this message]
2006-06-27 12:02       ` castet.matthieu
2006-06-27 14:19         ` Uwe Bugla
2006-06-27 16:03         ` Bjorn Helgaas
2006-06-28  1:02         ` Shaohua Li
2006-06-28  8:57           ` Uwe Bugla
2006-06-28 16:55           ` Bjorn Helgaas
2006-06-29  1:13             ` Shaohua Li
2006-06-29 12:24               ` Uwe Bugla
2006-06-29 18:38               ` Bjorn Helgaas
2006-06-30  1:30                 ` Shaohua Li
  -- strict thread matches above, loose matches on Subject: below --
2006-06-29 12:41 Li, Shaohua
2006-06-30  9:04 ` Uwe Bugla
2006-06-30 16:03   ` Bjorn Helgaas
2006-06-24 23:36 akpm

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=1151393390.21189.59.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@osdl.org \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=castet.matthieu@free.fr \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=uwe.bugla@gmx.de \
    /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