On Wed, Mar 30, 2016 at 8:49 AM, Yong Li <sdliyong@xxxxxxxxx> wrote: > The current implementation only uses the first byte in val, > the second byte is always 0. Change it to use cpu_to_le16 > to write the two bytes into the register > > Signed-off-by: Yong Li <sdliyong@xxxxxxxxx> Patch applied to fixes with Phil's review tag. It is a regression, right? Should it be tagged for stable? 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 v2] gpio: pca953x: Use correct u16 value for register word write
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v2] gpio: pca953x: Use correct u16 value for register word write
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 1 Apr 2016 14:51:14 +0200
- In-reply-to: <1459320554-2455-1-git-send-email-sdliyong@gmail.com>
- Follow-Ups:
- References:
- Prev by Date: Re: [PATCH] pinctrl: bcm2835: Implement get_direction callback
- Next by Date: Re: [PATCH v2] gpio/ls1043a: Add compatible "fsl,qoriq-gpio" for ls1043a gpio nodes
- Previous by thread: Re: [PATCH v2] gpio: pca953x: Use correct u16 value for register word write
- Next by thread: Re: [PATCH v2] gpio: pca953x: Use correct u16 value for register word write
- Index(es):
 |