From: Manivannan Sadhasivam <mani@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Sui Jingfeng <suijingfeng@loongson.cn>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] PCI: Fix kernel-doc issues
Date: Fri, 12 Jan 2024 10:52:00 +0530 [thread overview]
Message-ID: <20240112052200.GA2970@thinkpad> (raw)
In-Reply-To: <20240111162850.2177655-1-helgaas@kernel.org>
On Thu, Jan 11, 2024 at 10:28:50AM -0600, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Fix kernel-doc issues reported by
> "find include -name \*pci\* | xargs scripts/kernel-doc -none":
>
> include/linux/pci.h:731: warning: Function parameter or member 'pdev' not described in 'pci_is_vga'
> include/linux/pci-epc.h:154: warning: Function parameter or member 'list_lock' not described in 'pci_epc'
> include/linux/pci-epf.h:83: warning: expecting prototype for struct pci_epf_event_ops. Prototype was for struct pci_epc_event_ops instead
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
> ---
> include/linux/pci-epc.h | 2 +-
> include/linux/pci-epf.h | 2 +-
> include/linux/pci.h | 1 +
> 3 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/pci-epc.h b/include/linux/pci-epc.h
> index 5cb694031072..bfe41b03b70c 100644
> --- a/include/linux/pci-epc.h
> +++ b/include/linux/pci-epc.h
> @@ -122,7 +122,7 @@ struct pci_epc_mem {
> * struct pci_epc - represents the PCI EPC device
> * @dev: PCI EPC device
> * @pci_epf: list of endpoint functions present in this EPC device
> - * list_lock: Mutex for protecting pci_epf list
> + * @list_lock: Mutex for protecting pci_epf list
> * @ops: function pointers for performing endpoint operations
> * @windows: array of address space of the endpoint controller
> * @mem: first window of the endpoint controller, which corresponds to
> diff --git a/include/linux/pci-epf.h b/include/linux/pci-epf.h
> index 3f44b6aec477..92d0b71d33d7 100644
> --- a/include/linux/pci-epf.h
> +++ b/include/linux/pci-epf.h
> @@ -68,7 +68,7 @@ struct pci_epf_ops {
> };
>
> /**
> - * struct pci_epf_event_ops - Callbacks for capturing the EPC events
> + * struct pci_epc_event_ops - Callbacks for capturing the EPC events
> * @core_init: Callback for the EPC initialization complete event
> * @link_up: Callback for the EPC link up event
> * @link_down: Callback for the EPC link down event
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 1a89dc66f89a..eb45087d7e00 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -715,6 +715,7 @@ static inline bool pci_is_bridge(struct pci_dev *dev)
>
> /**
> * pci_is_vga - check if the PCI device is a VGA device
> + * @pdev: PCI device
> *
> * The PCI Code and ID Assignment spec, r1.15, secs 1.4 and 1.1, define
> * VGA Base Class and Sub-Classes:
> --
> 2.34.1
>
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-01-12 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 16:28 [PATCH] PCI: Fix kernel-doc issues Bjorn Helgaas
2024-01-12 0:00 ` Randy Dunlap
2024-01-12 2:35 ` Sui Jingfeng
2024-01-12 5:22 ` Manivannan Sadhasivam [this message]
2024-01-12 17:09 ` 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=20240112052200.GA2970@thinkpad \
--to=mani@kernel.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=suijingfeng@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.