On Tuesday, June 21, 2016 10:51:00 AM CEST Michael Ellerman wrote:
> On Fri, 2016-06-17 at 12:46 +0200, Arnd Bergmann wrote:
> > On Friday, June 17, 2016 1:35:35 PM CEST Daniel Axtens wrote:
> > > > It would be better to fix the sparse compilation so the same endianess
> > > > is set that you get w
Hi Arnd,
> Something like the (untested) patch below, similar to how we
> already handle the word size and how some other architectures
> handle setting __BIG_ENDIAN__.
I tested this by reverting Michael's patch and applying yours.
Not only does it successfully fix the errors that patch fixes, i
On Fri, 2016-06-17 at 12:46 +0200, Arnd Bergmann wrote:
> On Friday, June 17, 2016 1:35:35 PM CEST Daniel Axtens wrote:
> > > It would be better to fix the sparse compilation so the same endianess
> > > is set that you get when calling gcc.
> >
> > I will definitely work on a patch to sparse! I'd
On Friday, June 17, 2016 1:35:35 PM CEST Daniel Axtens wrote:
> > It would be better to fix the sparse compilation so the same endianess
> > is set that you get when calling gcc.
>
> I will definitely work on a patch to sparse! I'd still like this or
> something like it to go in though, so we can
On Thu, 2016-06-16 at 15:05 +0200, Arnd Bergmann wrote:
> On Thursday, June 16, 2016 10:33:41 PM CEST Michael Ellerman wrote:
> > From: Daniel Axtens
> >
> > Sparse complains that it doesn't know what REG_BYTE is:
> >
> > arch/powerpc/kernel/align.c:313:29: error: undefined identifier 'REG_BYT
> It would be better to fix the sparse compilation so the same endianess
> is set that you get when calling gcc.
I will definitely work on a patch to sparse! I'd still like this or
something like it to go in though, so we can keep working on reducing
the sparse warning count while the sparse patch
On Thursday, June 16, 2016 10:33:41 PM CEST Michael Ellerman wrote:
> From: Daniel Axtens
>
> Sparse complains that it doesn't know what REG_BYTE is:
>
> arch/powerpc/kernel/align.c:313:29: error: undefined identifier 'REG_BYTE'
>
> REG_BYTE is defined differently based on whether we're compi
From: Daniel Axtens
Sparse complains that it doesn't know what REG_BYTE is:
arch/powerpc/kernel/align.c:313:29: error: undefined identifier 'REG_BYTE'
REG_BYTE is defined differently based on whether we're compiling for
LE, BE32 or BE64. Sparse apparently doesn't provide __BIG_ENDIAN__ or
__L