IIO: Fix adding more than one iio device eventset
in [Kernel]
|
Prev: [PATCH 08/13] sparc: Preemptible mmu_gather
Next: staging/dt3155: fix build error caused by {write|read}l change
From: Andrew Morton on 8 Apr 2010 15:50 On Wed, 07 Apr 2010 19:15:56 +0100 Jonathan Cameron <jic23(a)cam.ac.uk> wrote: > Thanks for the patch. The first bug was fixed by a patch from Sonic Zhang. > Andrew Morton picked it up so it is in the mm tree. Thanks for the report > of this particularly horrible bug though as had been there quite a while before > Sonic pointed it out! hm. Is it a "horrible bug"? I had assumed that it was a minor bug and had staged the patch for 2.6.35. Was that a mistake? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jonathan Cameron on 9 Apr 2010 09:40
On 04/08/10 20:48, Andrew Morton wrote: > On Wed, 07 Apr 2010 19:15:56 +0100 > Jonathan Cameron <jic23(a)cam.ac.uk> wrote: > >> Thanks for the patch. The first bug was fixed by a patch from Sonic Zhang. >> Andrew Morton picked it up so it is in the mm tree. Thanks for the report >> of this particularly horrible bug though as had been there quite a while before >> Sonic pointed it out! > > hm. Is it a "horrible bug"? I had assumed that it was a minor bug and > had staged the patch for 2.6.35. Was that a mistake? > It is a bug you will only see if you attempt to bring up two iio devices with event interfaces at the same time. I've no idea if anyone has a, non-dev board where this is happening. If you trigger the bug the second devices probe will fail. So moderately horrible but the problem is fairly self contained. By the look of it two people have run into the bug (or spotted the problem during code review?) so probably worth pushing the fix in sooner rather than later. Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |