[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161019125742.GM4469@mwanda>
Date: Wed, 19 Oct 2016 15:57:43 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Brian Masney <masneyb@...tation.org>
Cc: devel@...verdev.osuosl.org, lars@...afoo.de,
linux-iio@...r.kernel.org, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, pmeerw@...erw.net, knaack.h@....de,
jic23@...nel.org
Subject: Re: [PATCH 5/7] iio: light: tsl2583: check return values from
taos_chip_{on, off}
On Wed, Oct 19, 2016 at 03:54:23PM +0300, Dan Carpenter wrote:
> On Wed, Oct 19, 2016 at 08:48:32AM -0400, Brian Masney wrote:
> > Ok, I'll rework my patch series to stick with the direct returns. I
> > personally prefer that approach. I was using the gotos since I thought
> > that was standard convention in the kernel.
> >
>
> It *should* but "goto unlock;"
s/but/be/
regards,
dan carpenter
Powered by blists - more mailing lists