From: "libaokun (A)" <libaokun1@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Wei Yongjun <weiyongjun1@huawei.com>,
"Yue Haibing" <yuehaibing@huawei.com>, <yangjihong1@huawei.com>,
yu kuai <yukuai3@huawei.com>
Subject: Re: [PATCH -next] acpi/nvs: fix doc warnings in nvs.c
Date: Tue, 15 Jun 2021 15:29:52 +0800 [thread overview]
Message-ID: <5114c2aa-e198-419f-c5f0-68e989dbb6fc@huawei.com> (raw)
In-Reply-To: <CAJZ5v0iPcSwjswJ7+1gPk-CKowLST7LG-4RQx_LkwFV+fUW6Gg@mail.gmail.com>
Thank you for your advice.
I'm about to send a patch v2 with the changes suggested by you.
Best Regards.
在 2021/6/9 21:12, Rafael J. Wysocki 写道:
> On Tue, Jun 8, 2021 at 4:29 AM Baokun Li <libaokun1@huawei.com> wrote:
>> Fixes the following W=1 kernel build warning(s):
>>
>> drivers/acpi/nvs.c:94: warning: Function parameter or
>> member 'start' not described in 'suspend_nvs_register'
>> drivers/acpi/nvs.c:94: warning: Function parameter or
>> member 'size' not described in 'suspend_nvs_register'
>>
>> Signed-off-by: Baokun Li <libaokun1@huawei.com>
>> ---
>> drivers/acpi/nvs.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/acpi/nvs.c b/drivers/acpi/nvs.c
>> index 9f8712a557b3..4609a8a2e42d 100644
>> --- a/drivers/acpi/nvs.c
>> +++ b/drivers/acpi/nvs.c
>> @@ -83,8 +83,8 @@ static LIST_HEAD(nvs_list);
>>
>> /**
>> * suspend_nvs_register - register platform NVS memory region to save
>> - * @start - physical address of the region
>> - * @size - size of the region
>> + * @start: physical address of the region
>> + * @size: size of the region
> The format of this kerneldoc comment is still not following the common
> style after your change.
>
> Please fix it completely.
>
>> *
>> * The NVS region need not be page-aligned (both ends) and we arrange
>> * things so that the data from page-aligned addresses in this region will
>> --
>> 2.31.1
>>
> .
prev parent reply other threads:[~2021-06-15 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 2:38 Baokun Li
2021-06-09 13:12 ` Rafael J. Wysocki
2021-06-15 7:29 ` libaokun (A) [this message]
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=5114c2aa-e198-419f-c5f0-68e989dbb6fc@huawei.com \
--to=libaokun1@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=weiyongjun1@huawei.com \
--cc=yangjihong1@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®