On Tue, Nov 8, 2016 at 6:18 AM, Phil Reid <preid@xxxxxxxxxxxxxxxxx> wrote: > Need to ensure that reg_output is not updated while setting multiple > bits. This makes the mutex locking behaviour for the set_multiple call > consistent with that of the set_value call. > > Signed-off-by: Phil Reid <preid@xxxxxxxxxxxxxxxxx> Patch applied for fixes. Stable? Fixes:? 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 1/1] gpio: pca953x: Move memcpy into mutex lock for set multiple function.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/1] gpio: pca953x: Move memcpy into mutex lock for set multiple function.
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Tue, 8 Nov 2016 09:32:26 +0100
- In-reply-to: <1478582291-57976-1-git-send-email-preid@electromag.com.au>
- References: <1478582291-57976-1-git-send-email-preid@electromag.com.au>
- Follow-Ups:
- References:
- Prev by Date: Re: [PATCH 1/1] gpio: pca953x: Fix corruption of other gpios in set_multiple.
- Next by Date: Re: [PATCH v2 01/15] pinctrl-sx150x: Improve OF device matching code
- Previous by thread: [PATCH 1/1] gpio: pca953x: Move memcpy into mutex lock for set multiple function.
- Next by thread: Re: [PATCH 1/1] gpio: pca953x: Move memcpy into mutex lock for set multiple function.
- Index(es):
 |