[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdYRqXuqqtVyPY_99tCEhX=wHKuQ0=m9ptVFHKOD4tUteQ@mail.gmail.com>
Date: Thu, 29 Aug 2013 19:21:21 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Sherman Yin <syin@...adcom.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Linus Walleij <linus.walleij@...ricsson.com>
Subject: Re: linux-next: manual merge of the pinctrl tree with Linus' tree
On Thu, Aug 29, 2013 at 7:20 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
>> Note the following return in between the locking and unlocking -
>> need an unlock there?
>>
>>> + case PIN_CONFIG_DRIVE_STRENGTH:
>>> + strength = pinconf_to_config_argument(configs[i]);
>>> + if (strength > 40)
>>> + return -EINVAL;
>
> Argh. Send a patch with your reported-by tag...
Not SEND, I mean SENT, I just SENT a patch...
subject "pinctrl: sunxi: drop lock on error path"
sorry for the confusion.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists