[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180112013408.GA6419@jagdpanzerIV>
Date: Fri, 12 Jan 2018 10:34:08 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Jesper Nilsson <jesper.nilsson@...s.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Mikael Starvik <starvik@...s.com>,
Jesper Nilsson <jespern@...s.com>,
Fenghua Yu <fenghua.yu@...el.com>, linux-cris-kernel@...s.com,
linux-kernel@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [PATCH] cris: Fix conflicting types for _etext, _edata, _end
On (01/11/18 15:24), Jesper Nilsson wrote:
> On Thu, Jan 11, 2018 at 11:12:51PM +0900, Sergey Senozhatsky wrote:
> > On (01/05/18 11:47), Sergey Senozhatsky wrote:
> > > Include asm/sections.h header which contains the correct
> > > types for _etext, _edata and _end - char arrays.
> > >
> > > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
> >
> > Mikael, Jesper,
> >
> > any opinions?
>
> This looks sane, and I can take it in the CRIS tree,
> allthough I'm currently pondering the future of the CRIS port,
> lack of time and active hardware are increasing problems.
ah, got it... didn't know that.
we have a number of patches in linux-next which introduce
some changes to commonly used header files and we saw build
errors on other platforms because of conflicting etext/etc
types. so I just grepped arch/ and applied the same fix to
CRIS.
-ss
Powered by blists - more mailing lists