linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org
Subject: [PATCH 06/10] of: address: Provide descriptions for 'of_address_to_resource's params
Date: Thu, 18 Mar 2021 10:40:32 +0000	[thread overview]
Message-ID: <20210318104036.3175910-7-lee.jones@linaro.org> (raw)
In-Reply-To: <20210318104036.3175910-1-lee.jones@linaro.org>

Fixes the following W=1 kernel build warning(s):

 drivers/of/address.c:868: warning: Function parameter or member 'dev' not described in 'of_address_to_resource'
 drivers/of/address.c:868: warning: Function parameter or member 'index' not described in 'of_address_to_resource'
 drivers/of/address.c:868: warning: Function parameter or member 'r' not described in 'of_address_to_resource'

Cc: Rob Herring <robh+dt@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>
Cc: devicetree@vger.kernel.org
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
 drivers/of/address.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/of/address.c b/drivers/of/address.c
index 73ddf2540f3fe..7de41abe7153f 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c
@@ -857,6 +857,9 @@ static int __of_address_to_resource(struct device_node *dev,
 
 /**
  * of_address_to_resource - Translate device tree address and return as resource
+ * @dev:	Caller's Device Node
+ * @index:	Index into the array
+ * @r:		Pointer to resource array
  *
  * Note that if your address is a PIO address, the conversion will fail if
  * the physical address can't be internally converted to an IO token with
-- 
2.27.0


  parent reply	other threads:[~2021-03-18 10:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 10:40 [PATCH v2 00/10] Rid W=1 warnings from OF Lee Jones
2021-03-18 10:40 ` [PATCH 01/10] of: device: Fix function name in header and provide missing descriptions Lee Jones
2021-03-18 10:40 ` [PATCH 02/10] of: dynamic: Fix incorrect parameter name " Lee Jones
2021-03-18 10:40 ` [PATCH 03/10] of: platform: Demote kernel-doc abuse Lee Jones
2021-03-18 10:40 ` [PATCH 04/10] of: base: Fix some formatting issues and provide missing descriptions Lee Jones
2021-03-18 10:40 ` [PATCH 05/10] of: property: Provide missing member description and remove excess param Lee Jones
2021-03-18 10:40 ` Lee Jones [this message]
2021-03-18 10:40 ` [PATCH 07/10] of: fdt: Demote kernel-doc abuses and fix function naming Lee Jones
2021-03-18 10:40 ` [PATCH 08/10] of: of_net: Provide function name and param description Lee Jones
2021-03-18 13:10   ` Andrew Lunn
2021-03-18 10:40 ` [PATCH 09/10] of: overlay: Fix function name disparity Lee Jones
2021-03-18 10:40 ` [PATCH 10/10] of: of_reserved_mem: Demote kernel-doc abuses Lee Jones
2021-03-22 22:22 ` [PATCH v2 00/10] Rid W=1 warnings from OF Rob Herring
2021-03-23  8:36   ` Lee Jones
2021-03-24 14:09     ` Rob Herring
2021-03-24 15:12       ` Lee Jones

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=20210318104036.3175910-7-lee.jones@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).