From: Alexey Kardashevskiy <aik@amd.com>
To: <linux-pci@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Lukas Wunner <lukas@wunner.de>,
Alexey Kardashevskiy <aik@amd.com>
Subject: [PATCH kernel 0/4] pci/doe/ide: Capabilities, protocols
Date: Thu, 1 Feb 2024 17:02:24 +1100 [thread overview]
Message-ID: <20240201060228.3070928-1-aik@amd.com> (raw)
Here are 4 small independent patches defining new PCIe caps and bits and
protocols, I am using them with my test device so they are real :)
Please comment. Thanks.
Alexey Kardashevskiy (4):
pci/doe: Define protocol types and make those public
pci/doe: Support discovery version
pci: Define TEE-IO bit in PCIe device capabilities
pci: Define Integrity and Data Encryption (IDE) extended capability
include/linux/pci-doe.h | 4 ++++
include/uapi/linux/pci_regs.h | 5 ++++-
drivers/pci/doe.c | 13 ++++++++-----
3 files changed, 16 insertions(+), 6 deletions(-)
--
2.41.0
next reply other threads:[~2024-02-01 6:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 6:02 Alexey Kardashevskiy [this message]
2024-02-01 6:02 ` [PATCH kernel 1/4] pci/doe: Define protocol types and make those public Alexey Kardashevskiy
2024-02-01 6:50 ` Lukas Wunner
2024-02-01 10:16 ` Alexey Kardashevskiy
2024-02-09 8:52 ` Lukas Wunner
2024-02-15 11:44 ` Alexey Kardashevskiy
2024-02-08 21:57 ` Bjorn Helgaas
2024-02-01 6:02 ` [PATCH kernel 2/4] pci/doe: Support discovery version Alexey Kardashevskiy
2024-02-08 22:00 ` Bjorn Helgaas
2024-02-01 6:02 ` [PATCH kernel 3/4] pci: Define TEE-IO bit in PCIe device capabilities Alexey Kardashevskiy
2024-02-01 6:02 ` [PATCH kernel 4/4] pci: Define Integrity and Data Encryption (IDE) extended capability Alexey Kardashevskiy
2024-02-08 22:02 ` Bjorn Helgaas
2024-02-08 21:55 ` [PATCH kernel 0/4] pci/doe/ide: Capabilities, protocols Bjorn Helgaas
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=20240201060228.3070928-1-aik@amd.com \
--to=aik@amd.com \
--cc=bhelgaas@google.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.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