From: Damien Le Moal <dlemoal@kernel.org>
To: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Manivannan Sadhasivami <manivannan.sadhasivam@linaro.org>
Subject: [PATCH 2/2] PCI: endpoint: Add kdoc description of pci_epf_type_add_cfs()
Date: Mon, 15 May 2023 14:15:00 +0900 [thread overview]
Message-ID: <20230515051500.574127-3-dlemoal@kernel.org> (raw)
In-Reply-To: <20230515051500.574127-1-dlemoal@kernel.org>
Restore an improve the kdoc function description for
pci_epf_type_add_cfs() that was removed with commit
893f14fed7d3 ("PCI: endpoint: Move pci_epf_type_add_cfs() code").
Fixes: 893f14fed7d3 ("PCI: endpoint: Move pci_epf_type_add_cfs() code")
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
---
drivers/pci/endpoint/pci-ep-cfs.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/drivers/pci/endpoint/pci-ep-cfs.c b/drivers/pci/endpoint/pci-ep-cfs.c
index d8a6abe2c31c..15e17a661875 100644
--- a/drivers/pci/endpoint/pci-ep-cfs.c
+++ b/drivers/pci/endpoint/pci-ep-cfs.c
@@ -509,6 +509,24 @@ static const struct config_item_type pci_epf_type = {
.ct_owner = THIS_MODULE,
};
+/**
+ * pci_epf_type_add_cfs() - Help function drivers to expose function specific
+ * attributes in configfs
+ * @epf: the EPF device that has to be configured using configfs
+ * @group: the parent configfs group (corresponding to entries in
+ * pci_epf_device_id)
+ *
+ * Invoke to expose function specific attributes in configfs.
+ *
+ * Return: NULL if the function driver
+ *
+ * Return: A pointer to a config_group structure or NULL if the function driver
+ * does not have anything to expose (attributes configured by user) or if the
+ * the function driver does not implement the add_cfs() method.
+ *
+ * Returns an error pointer if this function is called for an unbound EPF device
+ * or if the EPF driver add_cfs() method fails.
+ */
static struct config_group *pci_epf_type_add_cfs(struct pci_epf *epf,
struct config_group *group)
{
--
2.40.1
next prev parent reply other threads:[~2023-05-15 5:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 5:14 [PATCH 0/2] Fixup changes to pci_epf_type_add_cfs() Damien Le Moal
2023-05-15 5:14 ` [PATCH 1/2] PCI: endpoint: Improve pci_epf_type_add_cfs() Damien Le Moal
2023-05-15 7:19 ` Manivannan Sadhasivami
2023-05-15 7:31 ` Damien Le Moal
2023-05-15 5:15 ` Damien Le Moal [this message]
2023-05-15 7:21 ` [PATCH 2/2] PCI: endpoint: Add kdoc description of pci_epf_type_add_cfs() Manivannan Sadhasivami
2023-05-15 7:32 ` Damien Le Moal
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=20230515051500.574127-3-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=bhelgaas@google.com \
--cc=kishon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.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).