Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Alistair Francis <alistair@alistair23.me>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	Jonathan.Cameron@huawei.com, lukas@wunner.de,
	alex.williamson@redhat.com, christian.koenig@amd.com,
	kch@nvidia.com, gregkh@linuxfoundation.org, logang@deltatee.com,
	linux-kernel@vger.kernel.org, alistair23@gmail.com,
	chaitanyak@nvidia.com, rdunlap@infradead.org
Subject: Re: [PATCH v17 1/4] PCI/DOE: Rename DOE protocol to feature
Date: Thu, 6 Mar 2025 12:55:40 -0600	[thread overview]
Message-ID: <20250306185540.GA361668@bhelgaas> (raw)
In-Reply-To: <20250306075211.1855177-1-alistair@alistair23.me>

On Thu, Mar 06, 2025 at 05:52:08PM +1000, Alistair Francis wrote:
> DOE r1.1 replaced all occurrences of "protocol" with the term "feature"
> or "Data Object Type".
> 
> PCIe r6.1 (which was published July 24) incorporated that change.
> 
> Rename the existing terms protocol with feature.
> 
> Signed-off-by: Alistair Francis <alistair@alistair23.me>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Reviewed-by: Lukas Wunner <lukas@wunner.de>

All four patches applied to pci/doe for v6.15, thanks!

  [PATCH v17 1/4] PCI/DOE: Rename DOE protocol to feature
  [PATCH v17 2/4] PCI/DOE: Rename Discovery Response Data Object Contents to type
  [PATCH v17 3/4] PCI/DOE: Expose the DOE features via sysfs
  [PATCH v17 4/4] PCI/DOE: Allow enabling DOE without CXL


      parent reply	other threads:[~2025-03-06 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06  7:52 [PATCH v17 1/4] PCI/DOE: Rename DOE protocol to feature Alistair Francis
2025-03-06  7:52 ` [PATCH v17 2/4] PCI/DOE: Rename Discovery Response Data Object Contents to type Alistair Francis
2025-03-06  7:52 ` [PATCH v17 3/4] PCI/DOE: Expose the DOE features via sysfs Alistair Francis
2025-03-07 12:05   ` kernel test robot
2025-03-07 14:10   ` kernel test robot
2025-03-07 15:18   ` kernel test robot
2025-03-07 16:01   ` kernel test robot
2025-03-21 21:41   ` Bjorn Helgaas
2025-03-24  3:02     ` Alistair Francis
2025-03-06  7:52 ` [PATCH v17 4/4] PCI/DOE: Allow enabling DOE without CXL Alistair Francis
2025-03-06 18:55 ` 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=20250306185540.GA361668@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=alistair23@gmail.com \
    --cc=alistair@alistair23.me \
    --cc=bhelgaas@google.com \
    --cc=chaitanyak@nvidia.com \
    --cc=christian.koenig@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=lukas@wunner.de \
    --cc=rdunlap@infradead.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