From: Bjorn Helgaas <helgaas@kernel.org>
To: "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>,
"Wysocki, Rafael J" <rafael.j.wysocki@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 13:13:57 -0500 [thread overview]
Message-ID: <20220425181357.GA1647966@bhelgaas> (raw)
In-Reply-To: <4f277b84c2ee770f6a2706744b96fb1dfd6184a7.camel@intel.com>
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.
next prev parent reply other threads:[~2022-04-25 18:14 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 [this message]
2022-04-25 18:16 ` Dan Williams
2022-04-25 18:17 ` Rafael J. Wysocki
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=20220425181357.GA1647966@bhelgaas \
--to=helgaas@kernel.org \
--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=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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