I wonder, is this any better, or is there a recommended guideline somewhere? Testing against NULL at least highlights the fact that the variable is a pointer, this looks like valuable information to me. On Tue, Apr 7, 2015 at 11:22 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > On Tue, Mar 31, 2015 at 6:19 AM, Varka Bhadram <varkabhadram@xxxxxxxxx> wrote: > >> Signed-off-by: Varka Bhadram <varkab@xxxxxxx> > > Patch applied. > > Yours, > Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- From: Alexandre Courbot <gnurou@xxxxxxxxx>
- Date: Wed, 8 Apr 2015 10:50:03 +0900
- In-reply-to: <CACRpkdYR6RDfvK0t=EfLPw9FhW_GOoO9atY-AE7eBe74WvucBA@mail.gmail.com>
- Follow-Ups:
- Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- From: Linus Walleij
- Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- References:
- [PATCH gpio 0/4] cleanup for gpio drivers
- From: Varka Bhadram
- [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- From: Varka Bhadram
- Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- From: Linus Walleij
- [PATCH gpio 0/4] cleanup for gpio drivers
- Prev by Date: Re: [PATCH] fix platform_no_drv_owner.cocci warnings
- Next by Date: Re: [PATCH] pinctrl: Add support for PM8916 GPIO's and MPP's
- Previous by thread: Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- Next by thread: Re: [PATCH gpio 4/4] drivers: gpio: use (!foo) instead of (foo == NULL)
- Index(es):
 |