From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"Jonathan.Cameron@Huawei.com" <Jonathan.Cameron@Huawei.com>,
"a.manzanares@samsung.com" <a.manzanares@samsung.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"dave@stgolabs.net" <dave@stgolabs.net>
Subject: Re: [PATCH v6 0/3] PCI/ACPI: add support for CXL _OSC
Date: Mon, 25 Apr 2022 20:17:14 +0200 [thread overview]
Message-ID: <0ba818f7-6abe-4391-3fc0-788f58c5756b@intel.com> (raw)
In-Reply-To: <20220425181357.GA1647966@bhelgaas>
On 4/25/2022 8:13 PM, Bjorn Helgaas wrote:
> On Fri, Apr 22, 2022 at 10:24:34PM +0000, Verma, Vishal L wrote:
>> On Wed, 2022-04-13 at 01:36 -0600, Vishal Verma wrote:
>>> Changes since v5[1]:
>>> - Collect an reviewed-by tags from Rafael, Adam, and David
>>> - Fix a couple of missed s/CXL/extended/ in acpi_bus.h (Rafael)
>> Rafael, or Bjorn,
>>
>> Dan has offered to take this through cxl.git. Any objections to that -
>> would you prefer it to go through either the PCI or ACPI trees instead?
> OK by me if Dan or Rafael takes it.
All right, so it depends on whether or not there's any pending material
for the CXL tree that will depend on these patches. If so, it likely is
better to route them via CXL.
prev parent reply other threads:[~2022-04-25 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 7:36 [PATCH v6 0/3] PCI/ACPI: add support for CXL _OSC Vishal Verma
2022-04-13 7:36 ` [PATCH v6 1/3] PCI/ACPI: add a helper for retrieving _OSC Control DWORDs Vishal Verma
2022-04-13 7:36 ` [PATCH v6 2/3] PCI/ACPI: Prefer CXL _OSC instead of PCIe _OSC for CXL host bridges Vishal Verma
2022-04-13 7:36 ` [PATCH v6 3/3] PCI/ACPI: negotiate CXL _OSC Vishal Verma
2022-04-22 22:24 ` [PATCH v6 0/3] PCI/ACPI: add support for " Verma, Vishal L
2022-04-25 14:27 ` Rafael J. Wysocki
2022-04-25 18:13 ` Bjorn Helgaas
2022-04-25 18:16 ` Dan Williams
2022-04-25 18:17 ` Rafael J. Wysocki [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=0ba818f7-6abe-4391-3fc0-788f58c5756b@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=a.manzanares@samsung.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=vishal.l.verma@intel.com \
/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