From: Randy Dunlap <rdunlap@infradead.org>
To: linux-pci <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alexander Duyck <alexander.h.duyck@intel.com>
Subject: [PATCH] PCI: expand the "PF" acronym in Kconfig help text
Date: Sat, 6 Oct 2018 20:56:33 -0700 [thread overview]
Message-ID: <fceb7567-dae1-f393-b2e9-bce6e1fa5159@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Tell users what a PCI PF is in the PCI_PF_STUB config help text.
Fixes: a8ccf8a66663 ("PCI/IOV: Add pci-pf-stub driver for PFs that only enable VFs")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>
---
drivers/pci/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- lnx-419-rc6.orig/drivers/pci/Kconfig
+++ lnx-419-rc6/drivers/pci/Kconfig
@@ -73,9 +73,9 @@ config PCI_PF_STUB
depends on PCI_IOV
help
Say Y or M here if you want to enable support for devices that
- require SR-IOV support, while at the same time the PF itself is
- not providing any actual services on the host itself such as
- storage or networking.
+ require SR-IOV support, while at the same time the PF (Physical
+ Function) itself is not providing any actual services on the
+ host itself such as storage or networking.
When in doubt, say N.
next reply other threads:[~2018-10-07 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 3:56 Randy Dunlap [this message]
2018-10-07 17:02 ` [PATCH] PCI: expand the "PF" acronym in Kconfig help text Alexander Duyck
2018-10-08 17:33 ` 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=fceb7567-dae1-f393-b2e9-bce6e1fa5159@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--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).