From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: [PATCH 0/6] PCI/VPD: Further improvements
Date: Sun, 8 Aug 2021 19:18:08 +0200 [thread overview]
Message-ID: <1e61d5dc-824c-e855-01eb-6c7f45c55285@gmail.com> (raw)
This series includes a number of further improvements to VPD handling.
Heiner Kallweit (6):
PCI/VPD: Move pci_read/write_vpd in the code
PCI/VPD: Remove struct pci_vpd_ops
PCI/VPD: Remove member valid from struct pci_vpd
PCI/VPD: Embed struct pci_vpd member in struct pci_dev
PCI/VPD: Determine VPD size in pci_vpd_init already
PCI/VPD: Treat invalid VPD like no VPD capability
drivers/pci/probe.c | 1 -
drivers/pci/vpd.c | 253 ++++++++++++++++----------------------------
include/linux/pci.h | 9 +-
3 files changed, 97 insertions(+), 166 deletions(-)
--
2.32.0
next reply other threads:[~2021-08-08 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 17:18 Heiner Kallweit [this message]
2021-08-08 17:19 ` [PATCH 1/6] PCI/VPD: Move pci_read/write_vpd in the code Heiner Kallweit
2021-08-08 17:20 ` [PATCH 2/6] PCI/VPD: Remove struct pci_vpd_ops Heiner Kallweit
2021-08-11 22:00 ` Bjorn Helgaas
2021-08-11 23:43 ` Rustad, Mark D
2021-08-11 23:58 ` Alex Williamson
2021-08-08 17:21 ` [PATCH 3/6] PCI/VPD: Remove member valid from struct pci_vpd Heiner Kallweit
2021-08-08 17:21 ` [PATCH 4/6] PCI/VPD: Embed struct pci_vpd member in struct pci_dev Heiner Kallweit
2021-08-08 17:22 ` [PATCH 5/6] PCI/VPD: Determine VPD size in pci_vpd_init already Heiner Kallweit
2021-08-08 17:23 ` [PATCH 6/6] PCI/VPD: Treat invalid VPD like no VPD capability Heiner Kallweit
2021-08-12 17:53 ` [PATCH 0/6] PCI/VPD: Further improvements 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=1e61d5dc-824c-e855-01eb-6c7f45c55285@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).