From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/2] PNPACPI, x86/PCI: handle _CRS windows like Windows does
Date: Thu, 29 Apr 2010 09:42:16 -0600 [thread overview]
Message-ID: <201004290942.16739.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004282147490.2598@sony>
On Wednesday 28 April 2010 07:48:42 pm Len Brown wrote:
> applied both to acpi-test tree.
>
> you have pretty convincing evidence in the bug report that this is
> "corrrect" -- where "correct" = matches common industry practice.
>
> I wonder if this should wait for .35 or not...
I chatted with Jesse about this yesterday, and we plan to put the
x86/PCI part in .34. Actually, it looks like Linus has already
pulled it.
If you wanted to put the PNPACPI one in for .34, I wouldn't complain,
I guess, but I don't think we need it because I'm pretty sure nobody
actually relies on it. You'd be able to see the difference in
/sys/bus/pnp/devices/*/resources, but as far as I know, that's the only
place we'd notice.
Bjorn
prev parent reply other threads:[~2010-04-29 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 20:45 [PATCH 0/2] PNPACPI, x86/PCI: handle _CRS windows like Windows does Bjorn Helgaas
2010-04-27 20:45 ` [PATCH 1/2] PNPACPI: compute Address Space length rather than using _LEN Bjorn Helgaas
2010-04-27 20:45 ` [PATCH 2/2] x86/PCI: " Bjorn Helgaas
2010-04-29 1:48 ` [PATCH 0/2] PNPACPI, x86/PCI: handle _CRS windows like Windows does Len Brown
2010-04-29 15:42 ` Bjorn Helgaas [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=201004290942.16739.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.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.