public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-pci@vger.kernel.org, "Krzysztof Wilczyński" <kw@linux.com>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Niklas Cassel" <cassel@kernel.org>
Subject: Re: [PATCH v2] PCI: rockchip: Add missing fields descriptions for struct rockchip_pcie_ep
Date: Tue, 17 Dec 2024 10:19:05 +0530	[thread overview]
Message-ID: <20241217044905.g6cijdde6xqgdccn@thinkpad> (raw)
In-Reply-To: <20241216133404.540736-1-dlemoal@kernel.org>

On Mon, Dec 16, 2024 at 10:34:04PM +0900, Damien Le Moal wrote:
> When compiling the rockchip endpoint driver with -W=1, gcc output the
> following warnings:
> 
> drivers/pci/controller/pcie-rockchip-ep.c:59: warning: Function parameter or struct member 'perst_irq' not described in 'rockchip_pcie_ep'
> drivers/pci/controller/pcie-rockchip-ep.c:59: warning: Function parameter or struct member 'perst_asserted' not described in 'rockchip_pcie_ep'
> drivers/pci/controller/pcie-rockchip-ep.c:59: warning: Function parameter or struct member 'link_up' not described in 'rockchip_pcie_ep'
> drivers/pci/controller/pcie-rockchip-ep.c:59: warning: Function parameter or struct member 'link_training' not described in 'rockchip_pcie_ep'
> 
> Avoid these warnings by adding the missing field descriptions in
> struct rockchip_pcie_ep kdoc comment.
> 
> Reported-by: Bjorn Helgaas <helgaas@kernel.org>
> Fixes: a7137cbf6bd5 ("PCI: rockchip-ep: Handle PERST# signal in EP mode")
> Fixes: bd6e61df4b2e ("PCI: rockchip-ep: Improve link training")
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>

Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>

- Mani

> ---
> Changes from v1:
>  - Addressed Manivannan's comments
> 
>  drivers/pci/controller/pcie-rockchip-ep.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/pci/controller/pcie-rockchip-ep.c b/drivers/pci/controller/pcie-rockchip-ep.c
> index 1064b7b06cef..4f978a17fdbb 100644
> --- a/drivers/pci/controller/pcie-rockchip-ep.c
> +++ b/drivers/pci/controller/pcie-rockchip-ep.c
> @@ -40,6 +40,10 @@
>   * @irq_pci_fn: the latest PCI function that has updated the mapping of
>   *		the MSI/INTX IRQ dedicated outbound region.
>   * @irq_pending: bitmask of asserted INTX IRQs.
> + * @perst_irq: IRQ used for the PERST# signal.
> + * @perst_asserted: True if the PERST# signal was asserted.
> + * @link_up: True if the PCI link is up.
> + * @link_training: Work item to execute PCI link training.
>   */
>  struct rockchip_pcie_ep {
>  	struct rockchip_pcie	rockchip;
> -- 
> 2.47.1
> 

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2024-12-17  4:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 13:34 [PATCH v2] PCI: rockchip: Add missing fields descriptions for struct rockchip_pcie_ep Damien Le Moal
2024-12-17  4:49 ` Manivannan Sadhasivam [this message]
2024-12-22 21:12 ` Krzysztof Wilczyński

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=20241217044905.g6cijdde6xqgdccn@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=kishon@kernel.org \
    --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