linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Ricard <christophe.ricard@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
	Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/5] NFC: st21nfca: Fix obvious typo when check error code
Date: Mon, 20 Mar 2017 19:29:33 -0700	[thread overview]
Message-ID: <01ecc522-3b0e-a7af-1025-c249a79664dc@gmail.com> (raw)
In-Reply-To: <1489765790.19767.62.camel@linux.intel.com>

Hi Andy,

The patch looks good to me.

The device got enumerated via ACPI on development platforms for 
integration tests purposes.

Best Regards

Christophe

On 17/03/2017 08:49, Andy Shevchenko wrote:
> On Tue, 2017-03-07 at 12:25 +0200, Andy Shevchenko wrote:
>> We return -ENODEV if ACPI provides a GPIO resource. Looks really
>> wrong.
>> If it has even been tested?
> Any comments on this clean up?
>
> Next patch which is dependent to this is related to ACPI enumeration.
> After GPIO ACPI library gets stricter the driver wouldn't work without
> ACPI related changes.
>
> By the way, is this device have ever been enumerated via ACPI?
>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>>   drivers/nfc/st21nfca/i2c.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/nfc/st21nfca/i2c.c b/drivers/nfc/st21nfca/i2c.c
>> index 5a82f553906c..737384d287aa 100644
>> --- a/drivers/nfc/st21nfca/i2c.c
>> +++ b/drivers/nfc/st21nfca/i2c.c
>> @@ -514,9 +514,9 @@ static int
>> st21nfca_hci_i2c_acpi_request_resources(struct i2c_client *client)
>>   	/* Get EN GPIO from ACPI */
>>   	gpiod_ena = devm_gpiod_get_index(dev, ST21NFCA_GPIO_NAME_EN,
>> 1,
>>   					 GPIOD_OUT_LOW);
>> -	if (!IS_ERR(gpiod_ena)) {
>> +	if (IS_ERR(gpiod_ena)) {
>>   		nfc_err(dev, "Unable to get ENABLE GPIO\n");
>> -		return -ENODEV;
>> +		return PTR_ERR(gpiod_ena);
>>   	}
>>   
>>   	phy->gpio_ena = desc_to_gpio(gpiod_ena);

  reply	other threads:[~2017-03-21  2:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 10:25 [PATCH v2 1/5] NFC: st21nfca: Fix obvious typo when check error code Andy Shevchenko
2017-03-07 10:25 ` [PATCH v2 2/5] NFC: st21nfca: Get rid of platform data Andy Shevchenko
2017-03-07 10:25 ` [PATCH v2 3/5] NFC: st21nfca: Get rid of "interesting" use of interrupt polarity Andy Shevchenko
2017-03-07 10:25 ` [PATCH v2 4/5] NFC: st21nfca: Covert to use GPIO descriptor Andy Shevchenko
2017-03-07 10:25 ` [PATCH v2 5/5] NFC: st21nfca: Use unified device property API meaningfully Andy Shevchenko
2017-03-17 15:49 ` [PATCH v2 1/5] NFC: st21nfca: Fix obvious typo when check error code Andy Shevchenko
2017-03-21  2:29   ` Christophe Ricard [this message]
2017-03-21 18:36     ` Andy Shevchenko
2017-04-04 16:16 ` Andy Shevchenko
2017-04-05  8:09 ` Samuel Ortiz

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=01ecc522-3b0e-a7af-1025-c249a79664dc@gmail.com \
    --to=christophe.ricard@gmail.com \
    --cc=aloisio.almeida@openbossa.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.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;
as well as URLs for NNTP newsgroup(s).