linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-wireless@vger.kernel.org, julian.calaby@gmail.com
Subject: Re: [PATCH v2 1/2] staging: wilc1000: fix error handling in wilc_debugfs_init()
Date: Mon, 27 Jun 2016 14:02:09 +0100	[thread overview]
Message-ID: <577123D1.2020708@osg.samsung.com> (raw)
In-Reply-To: <20160625221659.GA11632@kroah.com>

On 25/06/16 23:16, Greg KH wrote:
> On Sat, Jun 25, 2016 at 10:43:33PM +0100, Luis de Bethencourt wrote:
>> On 25/06/16 22:36, Greg KH wrote:
>>> On Thu, Jun 23, 2016 at 01:36:17PM +0100, Luis de Bethencourt wrote:
>>>> The common format to check if a function returned an error pointer is to
>>>> use PTR_ERR(). Instead of ERR_PTR() which is used to return said errors.
>>>>
>>>> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
>>>> Reviewed-by: Julian Calaby <julian.calaby@gmail.com>
>>>> ---
>>>>  drivers/staging/wilc1000/wilc_debugfs.c | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/staging/wilc1000/wilc_debugfs.c b/drivers/staging/wilc1000/wilc_debugfs.c
>>>> index fcbc95d..48797dc 100644
>>>> --- a/drivers/staging/wilc1000/wilc_debugfs.c
>>>> +++ b/drivers/staging/wilc1000/wilc_debugfs.c
>>>> @@ -107,7 +107,7 @@ static int __init wilc_debugfs_init(void)
>>>>  	struct wilc_debugfs_info_t *info;
>>>>  
>>>>  	wilc_dir = debugfs_create_dir("wilc_wifi", NULL);
>>>> -	if (wilc_dir ==  ERR_PTR(-ENODEV)) {
>>>> +	if (PTR_ERR(wilc_dir) == -ENODEV) {
>>>>  		/* it's not error. the debugfs is just not being enabled. */
>>>>  		printk("ERR, kernel has built without debugfs support\n");
>>>>  		return 0;
>>>
>>> No, the best way to do this is to just ignore the return value, you
>>> don't care about it.  It can be passed back into any debugfs calls just
>>> fine.
>>>
>>> So don't check the value and all is good, debugfs was written in a way
>>> to make it _easy_ to use, no need for fancy error checking at all with
>>> it.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>
>> Thanks for the review Greg.
>>
>> Just to make sure. You are proposing I just drop the 3 if checks? [0]
>>
>> If that's what you mean I will send a patch as soon as you confirm :)
>>
>> Happy hacking,
>> Luis
>>
>>
>>
>> [0] Making the function look like this:
>> static int __init wilc_debugfs_init(void)
>> {
>>         int i;
>>
>>         struct dentry *debugfs_files;
>>         struct wilc_debugfs_info_t *info;
>>
>>         wilc_dir = debugfs_create_dir("wilc_wifi", NULL);
>>         for (i = 0; i < ARRAY_SIZE(debugfs_info); i++) {
>>                 info = &debugfs_info[i];
>>                 debugfs_files = debugfs_create_file(info->name,
>>                                                     info->perm,
>>                                                     wilc_dir,
>>                                                     &info->data,
>>                                                     &info->fops);
> 
> Why even assign anything to debugfs_files?
> 

Sorry Greg.

I was just confirming I understood your suggestion, and pasted that
without cleaning the code.

Thanks for review and idea!
Luis

      reply	other threads:[~2016-06-27 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 12:36 [PATCH v2 1/2] staging: wilc1000: fix error handling in wilc_debugfs_init() Luis de Bethencourt
2016-06-23 12:36 ` [PATCH v2 2/2] staging: wilc1000: fix error values " Luis de Bethencourt
2016-06-25 21:36   ` Greg KH
2016-06-25 21:36 ` [PATCH v2 1/2] staging: wilc1000: fix error handling " Greg KH
2016-06-25 21:43   ` Luis de Bethencourt
2016-06-25 22:16     ` Greg KH
2016-06-27 13:02       ` Luis de Bethencourt [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=577123D1.2020708@osg.samsung.com \
    --to=luisbg@osg.samsung.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=julian.calaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).