Re: [PATCH 1/2] gpio: menz127: Drop lock field from struct men_z127_gpio

[Linus Walleij <linus.walleij@xxxxxxxxxx>]

On Tue, Mar 22, 2016 at 11:53 AM, Axel Lin <axel.lin@xxxxxxxxxx> wrote:
> 2016-03-22 18:31 GMT+08:00 Linus Walleij <linus.walleij@xxxxxxxxxx>:
>> On Wed, Mar 9, 2016 at 1:38 PM, Axel Lin <axel.lin@xxxxxxxxxx> wrote:
>>
>>> Current code uses a uninitialized spin lock.
>>> bgpio_init() already initialized a spin lock, so let's switch to use
>>> &gc->bgpio_lock instead and remove the lock from struct men_z127_gpio.
>>>
>>> Signed-off-by: Axel Lin <axel.lin@xxxxxxxxxx>
>>
>> Patch applied for the v4.7 cycle. Will not appear in -next until
>> after -rc1.
>
> Is it fine to use uninitialized spinlock?
> If not, this one should be for 4.6.

Ah, I see, moving it to fixes, tagging for stable.

When you find stuff like this, put in Cc: stable@xxxxxxxxxxxxxxx
please, then I know immediately what to do with it :)

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