From: Hanjun Guo <guohanjun@huawei.com>
To: Shiju Jose <shiju.jose@huawei.com>, <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <lorenzo.pieralisi@arm.com>,
<sudeep.holla@arm.com>, <rjw@rjwysocki.net>, <lenb@kernel.org>
Cc: <linuxarm@huawei.com>
Subject: Re: [PATCH 1/1] ACPI/IORT: Fix doc warnings in iort.c
Date: Fri, 16 Oct 2020 14:59:16 +0800 [thread overview]
Message-ID: <c4987f7a-49b6-7c80-911d-1703fb6eb892@huawei.com> (raw)
In-Reply-To: <20201014093139.1580-1-shiju.jose@huawei.com>
On 2020/10/14 17:31, Shiju Jose wrote:
> Fix following warnings caused by mismatch between
> function parameters and function comments.
>
> drivers/acpi/arm64/iort.c:55: warning: Function parameter or member 'iort_node' not described in 'iort_set_fwnode'
> drivers/acpi/arm64/iort.c:55: warning: Excess function parameter 'node' description in 'iort_set_fwnode'
> drivers/acpi/arm64/iort.c:682: warning: Function parameter or member 'id' not described in 'iort_get_device_domain'
> drivers/acpi/arm64/iort.c:682: warning: Function parameter or member 'bus_token' not described in 'iort_get_device_domain'
> drivers/acpi/arm64/iort.c:682: warning: Excess function parameter 'req_id' description in 'iort_get_device_domain'
> drivers/acpi/arm64/iort.c:1142: warning: Function parameter or member 'dma_size' not described in 'iort_dma_setup'
> drivers/acpi/arm64/iort.c:1142: warning: Excess function parameter 'size' description in 'iort_dma_setup'
> drivers/acpi/arm64/iort.c:1534: warning: Function parameter or member 'ops' not described in 'iort_add_platform_device'
>
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
Acked-by: Hanjun Guo <guohanjun@huawei.com>
next prev parent reply other threads:[~2020-10-16 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 9:31 [PATCH 1/1] ACPI/IORT: Fix doc warnings in iort.c Shiju Jose
2020-10-16 6:59 ` Hanjun Guo [this message]
2020-11-19 18:01 ` Lorenzo Pieralisi
2020-11-19 18:03 ` Catalin Marinas
2020-11-19 18:09 ` Lorenzo Pieralisi
2020-11-20 9:49 ` Will Deacon
2020-11-23 11:27 ` Will Deacon
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=c4987f7a-49b6-7c80-911d-1703fb6eb892@huawei.com \
--to=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=shiju.jose@huawei.com \
--cc=sudeep.holla@arm.com \
/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).