linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	"Krzysztof Wilczyński" <kw@linux.com>
Subject: Re: [PATCH v2 0/2] PCI/VPD: Improve handling binary sysfs attribute
Date: Tue, 30 Mar 2021 16:53:30 -0500	[thread overview]
Message-ID: <20210330215330.GA1320710@bjorn-Precision-5520> (raw)
In-Reply-To: <305704a7-f1da-a5a0-04e6-ee884be4f6da@gmail.com>

On Wed, Feb 03, 2021 at 09:46:58AM +0100, Heiner Kallweit wrote:
> Since 104daa71b396 ("PCI: Determine actual VPD size on first access")
> there's nothing that keeps us from using a static attribute.
> This allows to significantly simplify the code.
> 
> v2:
> - switch to using PCI sysfs core code in patch 2
> 
> Heiner Kallweit (2):
>   PCI/VPD: Remove dead code from sysfs access functions
>   PCI/VPD: Let PCI sysfs core code handle VPD binary attribute
> 
>  drivers/pci/pci-sysfs.c | 54 +++++++++++++++++++++++---------
>  drivers/pci/pci.h       |  2 --
>  drivers/pci/vpd.c       | 68 -----------------------------------------
>  3 files changed, 40 insertions(+), 84 deletions(-)

Applied to pci/vpd for v5.13, thanks!

      parent reply	other threads:[~2021-03-30 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  8:46 [PATCH v2 0/2] PCI/VPD: Improve handling binary sysfs attribute Heiner Kallweit
2021-02-03  8:48 ` [PATCH v2 1/2] PCI/VPD: Remove dead code from sysfs access functions Heiner Kallweit
2021-02-03 15:22   ` Krzysztof Wilczyński
2021-02-03  8:50 ` [PATCH v2 2/2] PCI/VPD: Let PCI sysfs core code handle VPD binary attribute Heiner Kallweit
2021-02-03 15:24   ` Krzysztof Wilczyński
2021-03-30 21:53 ` 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=20210330215330.GA1320710@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kw@linux.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).