From: Bjorn Helgaas <helgaas@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 0/5] PCI/VPD: Further improvements
Date: Thu, 5 Aug 2021 14:29:38 -0500 [thread overview]
Message-ID: <20210805192938.GA1777404@bjorn-Precision-5520> (raw)
In-Reply-To: <b22a2ef2-2a32-410a-2680-ca05d7b52df3@gmail.com>
On Thu, Aug 05, 2021 at 09:10:51PM +0200, Heiner Kallweit wrote:
> On 03.08.2021 00:32, Bjorn Helgaas wrote:
> > On Thu, May 13, 2021 at 10:53:44PM +0200, Heiner Kallweit wrote:
> >> Series with further improvements to PCI VPD handling.
> >>
> >> Heiner Kallweit (5):
> >> PCI/VPD: Refactor pci_vpd_size
> >> PCI: Clean up VPD constants and functions in pci.h
> >> PCI/VPD: Remove old_size argument from pci_vpd_size
> >> PCI/VPD: Make pci_vpd_wait uninterruptible
> >> PCI/VPD: Remove pci_vpd member flag
> >>
> >> drivers/pci/vpd.c | 106 ++++++++++++++++----------------------------
> >> include/linux/pci.h | 43 ------------------
> >> 2 files changed, 37 insertions(+), 112 deletions(-)
> >
> > Applied to pci/vpd for v5.15, thanks!
> >
> pci/vpd hasn't been merged yet into next, is this intentional?
I let the 0-day bot build things before merging into next. But thanks
for the reminder, there are a couple branches I should merge.
Bjorn
prev parent reply other threads:[~2021-08-05 19:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 20:53 [PATCH 0/5] PCI/VPD: Further improvements Heiner Kallweit
2021-05-13 20:55 ` [PATCH 2/5] PCI: Clean up VPD constants and functions in pci.h Heiner Kallweit
2021-07-14 16:43 ` Bjorn Helgaas
2021-05-13 20:56 ` [PATCH 3/5] PCI/VPD: Remove old_size argument from pci_vpd_size Heiner Kallweit
2021-05-13 20:56 ` [PATCH 4/5] PCI/VPD: Make pci_vpd_wait uninterruptible Heiner Kallweit
2021-05-13 20:58 ` [PATCH 1/5] PCI/VPD: Refactor pci_vpd_size Heiner Kallweit
2021-07-13 20:25 ` Bjorn Helgaas
2021-07-13 21:13 ` Heiner Kallweit
2021-07-14 15:50 ` Bjorn Helgaas
2021-07-15 8:31 ` Heiner Kallweit
2021-05-13 21:02 ` [PATCH 5/5] PCI/VPD: Remove pci_vpd member flag Heiner Kallweit
2021-07-06 5:56 ` [PATCH 0/5] PCI/VPD: Further improvements Heiner Kallweit
2021-07-06 14:32 ` Bjorn Helgaas
2021-07-15 21:59 ` [PATCH 0/5] PCI/VPD: pci_vpd_size() cleanups Bjorn Helgaas
2021-07-15 21:59 ` [PATCH 1/5] PCI/VPD: Correct diagnostic for VPD read failure Bjorn Helgaas
2021-07-15 22:07 ` Heiner Kallweit
2021-07-16 5:58 ` Hannes Reinecke
2021-07-15 21:59 ` [PATCH 2/5] PCI/VPD: Check Resource tags against those valid for type Bjorn Helgaas
2021-07-16 5:59 ` Hannes Reinecke
2021-07-15 21:59 ` [PATCH 3/5] PCI/VPD: Consolidate missing EEPROM checks Bjorn Helgaas
2021-07-15 22:16 ` Heiner Kallweit
2021-07-28 23:42 ` Bjorn Helgaas
2021-07-29 6:10 ` Heiner Kallweit
2021-07-29 18:31 ` Bjorn Helgaas
2021-07-16 6:00 ` Hannes Reinecke
2021-07-15 21:59 ` [PATCH 4/5] PCI/VPD: Don't check Large Resource types for validity Bjorn Helgaas
2021-07-16 6:03 ` Hannes Reinecke
2021-07-28 23:46 ` Bjorn Helgaas
2021-07-15 21:59 ` [PATCH 5/5] PCI/VPD: Allow access to valid parts of VPD if some is invalid Bjorn Helgaas
2021-07-16 6:04 ` Hannes Reinecke
2021-08-02 22:32 ` [PATCH 0/5] PCI/VPD: Further improvements Bjorn Helgaas
2021-08-05 19:10 ` Heiner Kallweit
2021-08-05 19:29 ` 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=20210805192938.GA1777404@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=hkallweit1@gmail.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