RE: bit fields && data tearing

Paul E. McKenney wrote: >On Fri, Sep 05, 2014 at 02:50:31PM -0400, Peter Hurley wrote: >>On 09/05/2014 02:09 PM, Paul E. McKenney wrote: >>> This commit documents the fact that it is not safe to use bitfields as >>> shared variables in synchronization algorithms. It also documents that >>> CPUs mu

Re: Build regressions/improvements in v3.10

Geert, Bjorn, Geert Uytterhoeven wrote: > On Tue, Jul 2, 2013 at 8:34 PM, Bjorn Helgaas > wrote: > >> + warning: vmlinux.o(.text+0x1ad7a4): Section mismatch > in reference from the function pwmchip_add() to the function > .init.text:pcibios_fixup_bus(): => N/A > >> + warning: vmlinux.o(.text

RE: [PATCH] tile: support GENERIC_KERNEL_THREAD and GENERIC_KERNEL_EXECVE

Jeff King wrote: > On Tue, Oct 23, 2012 at 11:25:06PM +0200, Thomas Gleixner wrote: > > > The resulting notes are stored in a separate > > > revision-controlled branch > > > > Which branch(es) is/are that ? What are the semantics of that? [...] Nice feature. Can a later commit be eventually be m

RE: [LKML] Re: Build regressions/improvements in v3.6

Geert Uytterhoeven wrote: > xtensa-allmodconfig (hmm, this is not a new one, it felt through the > cracks in -rc7 because of log line interleaving). > > Ugh, arch/xtensa/include/asm/regs.h defines way to generic symbols, > like "MISC" (which causes the above breakage), and even a few > 2-letter sy

Re: xtensa port maintenance

Chris Zankel wrote: > I have set up a tree on github for now, and will work close > with Max to get his changes to Stephen's linux-next tree and > eventually Linus' tree. > I think it's fine to add Max as a second maintainer [...] Thanks for helping! Pete Delaney wrote: > I'm afraid that doing i