public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: bhelgaas@google.com, lenb@kernel.org, yinghai@kernel.org,
	izumi.taku@jp.fujitsu.com, jiang.liu@huawei.com,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix a hard coding style when determining if a device is a container.
Date: Fri, 12 Oct 2012 18:47:30 +0800	[thread overview]
Message-ID: <5077F542.3010003@cn.fujitsu.com> (raw)
In-Reply-To: <5077ECA6.4010302@jp.fujitsu.com>

On 10/12/2012 06:10 PM, Yasuaki Ishimatsu wrote:
> Hi Tang,
> 
> 2012/10/12 15:55, Tang Chen wrote:
>> "ACPI0004","PNP0A05" and "PNP0A06" are all defined in array
>> container_device_ids[], so use it, but not the hard coding style.
> 
> The idea is good.
> 
>>
>> Signed-off-by: Tang Chen<tangchen@cn.fujitsu.com>
>> ---
>>    drivers/acpi/container.c |   10 +++++++---
>>    1 files changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/acpi/container.c b/drivers/acpi/container.c
>> index 1f9f7d7..448c0e2 100644
>> --- a/drivers/acpi/container.c
>> +++ b/drivers/acpi/container.c
>> @@ -217,6 +217,7 @@ container_walk_namespace_cb(acpi_handle handle,
>>    {
>>    	char *hid = NULL;
>>    	struct acpi_device_info *info;
>> +	struct acpi_device_id *container_id;
>>    	acpi_status status;
>>    	int *action = context;
>>
>> @@ -232,10 +233,13 @@ container_walk_namespace_cb(acpi_handle handle,
>>    		goto end;
>>    	}
>>
>> -	if (strcmp(hid, "ACPI0004")&&  strcmp(hid, "PNP0A05")&&
>> -	    strcmp(hid, "PNP0A06")) {
>> -		goto end;
>> +	for (container_id = container_device_ids;
>> +	     container_id->id[0]; container_id++) {
>> +		if (!strcmp((char *)container_id->id, hid))
>> +			break;
>>    	}
>> +	if (!container_id->id[0])
>> +		goto end;
> 
> How about prepare is_container_device() function and check whether
> the device is the container device or not as below?

Sure. :)
A new patch will be sent soon.

Thanks for the wonderful idea. :)

> 
> 	if (is_container_device())
> 		goto end;
> 
> Thanks,
> Yasuaki Ishimatsu
> 
>>
>>    	switch (*action) {
>>    	case INSTALL_NOTIFY_HANDLER:
>>
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


      reply	other threads:[~2012-10-12 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  6:55 [PATCH] Fix a hard coding style when determining if a device is a container Tang Chen
2012-10-12 10:10 ` Yasuaki Ishimatsu
2012-10-12 10:47   ` 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=5077F542.3010003@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=bhelgaas@google.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yinghai@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