On Wed, Feb 1, 2017 at 8:47 AM, Alexander Stein <alexander.stein@xxxxxxxxxxxxxxxxxxxxx> wrote: > On Monday 30 January 2017 13:51:49, Mika Westerberg wrote: >> On Mon, Jan 30, 2017 at 12:35:28PM +0100, Alexander Stein wrote: >> > According to VLI64 Intel Atom E3800 Specification Update (#329901) >> > concurrent read accesses may result in returning 0xffffffff and write >> > accesses may be dropped silently. >> > To workaround all accesses must be protected by locks. >> > >> > Signed-off-by: Alexander Stein <alexander.stein@xxxxxxxxxxxxxxxxxxxxx> >> >> Acked-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> >> >> Should probably go to stable as well. > > Sure, but I don't know which stable kernels this should go in. More often than not, I *think* Greg will figure that out by: "does it apply?" "then yes" 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