On Wed, Apr 24, 2013 at 05:53:08PM +0200, Andreas Larsson wrote: > Commit aea1181b0bd0a09c54546399768f359d1e198e45 upstream > > [Backport to 3.0.y. Needed to compile ext4 for sparc32 since commit > 503f4bdcc078e7abee273a85ce322de81b18a224] > > There is no-one that really require atomic64_t support on sparc32. > But several drivers fails to build without proper atomic64 support. > And for an allyesconfig build for sparc32 this is annoying. > > Include the generic atomic64_t support for sparc32. > This has a text footprint cost: > > $size vmlinux (before atomic64_t support) > text data bss dec hex filename > 3578860 134260 108781 3821901 3a514d vmlinux > > $size vmlinux (after atomic64_t support) > text data bss dec hex filename > 3579892 130684 108781 3819357 3a475d vmlinux > > text increase (3579892 - 3578860) = 1032 bytes > > data decreases - but I fail to explain why! > I have rebuild twice to check my numbers. > > Signed-off-by: Sam Ravnborg <sam@xxxxxxxxxxxx> > Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx> > Signed-off-by: Andreas Larsson <andreas@xxxxxxxxxxx> > --- > > If this is an incorrect way to submit a backport of someone elses patch > to stable, please let me know. The Signed-off-by from Sam and David are > for the upstream patch. I need an ack from David before I can take this, as he normally sends the sparc stable patches to me. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html