linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: rjw@sisk.pl, lenb@kernel.org, toshi.kani@hp.com,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: Return -ENOENT in acpi_table_parse() and fix wrong comment.
Date: Tue, 07 Jan 2014 12:50:06 +0800	[thread overview]
Message-ID: <52CB877E.4030902@cn.fujitsu.com> (raw)
In-Reply-To: <2420572.xQX3sn8lDK@vostro.rjw.lan>

On 01/06/2014 07:50 PM, Rafael J. Wysocki wrote:
> On Monday, January 06, 2014 04:47:59 PM Tang Chen wrote:
>> The comment about return value of acpi_table_parse() is incorrect.
>> This patch fix it.
>>
>> Since all callers only check if the function succeeded or not, this
>> patch simplifies the semantics by returning -errno for all failure
>> cases. This will also simply the comment.
>>
>> As suggested by Toshi Kani<toshi.kani@hp.com>, also change the stub
>> in linux/acpi.h to return -ENODEV.
>>
>> Signed-off-by: Tang Chen<tangchen@cn.fujitsu.com>
>
> Queued up for 3.14 (but please use the e-mail address from MAINTAINERS next
> time) with a modified subject.  Thanks!

OK, will use the email address from MAINTAINERS next time.

Thanks.

>
>> ---
>>   drivers/acpi/tables.c | 7 ++++---
>>   include/linux/acpi.h  | 2 +-
>>   2 files changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c
>> index 5a5263b..10022ae 100644
>> --- a/drivers/acpi/tables.c
>> +++ b/drivers/acpi/tables.c
>> @@ -278,12 +278,13 @@ acpi_table_parse_madt(enum acpi_madt_type id,
>>
>>   /**
>>    * acpi_table_parse - find table with @id, run @handler on it
>> - *
>>    * @id: table id to find
>>    * @handler: handler to run
>>    *
>>    * Scan the ACPI System Descriptor Table (STD) for a table matching @id,
>> - * run @handler on it.  Return 0 if table found, return on if not.
>> + * run @handler on it.
>> + *
>> + * Return 0 if table found, -errno if not.
>>    */
>>   int __init acpi_table_parse(char *id, acpi_tbl_table_handler handler)
>>   {
>> @@ -306,7 +307,7 @@ int __init acpi_table_parse(char *id, acpi_tbl_table_handler handler)
>>   		early_acpi_os_unmap_memory(table, tbl_size);
>>   		return 0;
>>   	} else
>> -		return 1;
>> +		return -ENODEV;
>>   }
>>
>>   /*
>> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
>> index d9099b1..fecfbcd 100644
>> --- a/include/linux/acpi.h
>> +++ b/include/linux/acpi.h
>> @@ -460,7 +460,7 @@ struct acpi_table_header;
>>   static inline int acpi_table_parse(char *id,
>>   				int (*handler)(struct acpi_table_header *))
>>   {
>> -	return -1;
>> +	return -ENODEV;
>>   }
>>
>>   static inline int acpi_nvs_register(__u64 start, __u64 size)
>>
>

      reply	other threads:[~2014-01-07  4:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06  8:47 [PATCH] acpi: Return -ENOENT in acpi_table_parse() and fix wrong comment Tang Chen
2014-01-06 11:50 ` Rafael J. Wysocki
2014-01-07  4:50   ` Tang Chen [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=52CB877E.4030902@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rjw@sisk.pl \
    --cc=toshi.kani@hp.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).