From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] PCI/VPD: Encapsulate VPD stuff in vpd.c
Date: Mon, 19 Mar 2018 13:50:18 -0500 [thread overview]
Message-ID: <20180319185018.GC77194@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <152097990638.37832.15000151673990461303.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Tue, Mar 13, 2018 at 05:26:14PM -0500, Bjorn Helgaas wrote:
> This is strictly cleanup, not intended to change or fix anything.
>
> Move all the VPD-related code and structures to drivers/pci/vpd.c.
>
> ---
>
> Bjorn Helgaas (4):
> PCI/VPD: Move VPD access code to vpd.c
> PCI/VPD: Move VPD sysfs code to vpd.c
> PCI/VPD: Move VPD quirks to vpd.c
> PCI/VPD: Move VPD structures to vpd.c
Applied to pci/vpd for v4.17.
prev parent reply other threads:[~2018-03-19 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 22:26 [PATCH v1 0/4] PCI/VPD: Encapsulate VPD stuff in vpd.c Bjorn Helgaas
2018-03-13 22:26 ` [PATCH v1 1/4] PCI/VPD: Move VPD access code to vpd.c Bjorn Helgaas
2018-03-13 22:26 ` [PATCH v1 2/4] PCI/VPD: Move VPD sysfs " Bjorn Helgaas
2018-03-13 22:26 ` [PATCH v1 3/4] PCI/VPD: Move VPD quirks " Bjorn Helgaas
2018-03-13 22:27 ` [PATCH v1 4/4] PCI/VPD: Move VPD structures " Bjorn Helgaas
2018-03-19 18:50 ` 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=20180319185018.GC77194@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).