From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <robert.moore@intel.com>, <lv.zheng@intel.com>,
<rafael.j.wysocki@intel.com>, <lenb@kernel.org>
Subject: Re: [PATCH] acpica: trivial changes on comments
Date: Mon, 17 Apr 2017 10:58:30 +0800 [thread overview]
Message-ID: <58F42F56.2070809@cn.fujitsu.com> (raw)
In-Reply-To: <1492397781-18584-1-git-send-email-caoj.fnst@cn.fujitsu.com>
Re-to: linux-acpi@vger.kernel.org
On 04/17/2017 10:56 AM, Cao jin wrote:
> Remove superfluous word; unify comments and function prototype.
>
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> drivers/acpi/acpica/tbfadt.c | 2 +-
> drivers/acpi/acpica/tbutils.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/acpi/acpica/tbfadt.c b/drivers/acpi/acpica/tbfadt.c
> index 51860bf..ba5fcbe 100644
> --- a/drivers/acpi/acpica/tbfadt.c
> +++ b/drivers/acpi/acpica/tbfadt.c
> @@ -449,7 +449,7 @@ void acpi_tb_create_local_fadt(struct acpi_table_header *table, u32 length)
> * The 64-bit X fields are optional extensions to the original 32-bit FADT
> * V1.0 fields. Even if they are present in the FADT, they are optional and
> * are unused if the BIOS sets them to zero. Therefore, we must copy/expand
> - * 32-bit V1.0 fields to the 64-bit X fields if the the 64-bit X field is
> + * 32-bit V1.0 fields to the 64-bit X fields if the 64-bit X field is
> * originally zero.
> *
> * For ACPI 1.0 FADTs (that contain no 64-bit addresses), all 32-bit address
> diff --git a/drivers/acpi/acpica/tbutils.c b/drivers/acpi/acpica/tbutils.c
> index 5a968a7..e05555c 100644
> --- a/drivers/acpi/acpica/tbutils.c
> +++ b/drivers/acpi/acpica/tbutils.c
> @@ -141,7 +141,7 @@ void acpi_tb_check_dsdt_header(void)
> *
> * FUNCTION: acpi_tb_copy_dsdt
> *
> - * PARAMETERS: table_desc - Installed table to copy
> + * PARAMETERS: table_index - Index of installed table to copy
> *
> * RETURN: None
> *
> @@ -239,7 +239,7 @@ acpi_tb_get_root_table_entry(u8 *table_entry, u32 table_entry_size)
> *
> * FUNCTION: acpi_tb_parse_root_table
> *
> - * PARAMETERS: rsdp - Pointer to the RSDP
> + * PARAMETERS: rsdp_address - Pointer to the RSDP
> *
> * RETURN: Status
> *
>
--
Sincerely,
Cao jin
prev parent reply other threads:[~2017-04-17 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 2:56 Cao jin
2017-04-17 2:58 ` Cao jin [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=58F42F56.2070809@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.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
Powered by JetHome