Date: Fri, 12 Jan 2018 10:34:08 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Mikael Starvik <starvik@axis.com>,
        Jesper Nilsson <jespern@axis.com>,
        Fenghua Yu <fenghua.yu@intel.com>, linux-cris-kernel@axis.com,
        linux-kernel@vger.kernel.org,
        Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH] cris: Fix conflicting types for _etext, _edata, _end
Message-ID: <20180112013408.GA6419@jagdpanzerIV>
References: <20180105024744.17037-1-sergey.senozhatsky@gmail.com>
 <20180111141251.GA754@tigerII.localdomain>
 <20180111142423.GA32368@axis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180111142423.GA32368@axis.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org

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@gmail.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