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
Date: Fri, 12 Jan 2018 10:34:08 +0900 [thread overview]
Message-ID: <20180112013408.GA6419@jagdpanzerIV> (raw)
In-Reply-To: <20180111142423.GA32368@axis.com>
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
prev parent reply other threads:[~2018-01-12 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 2:47 [PATCH] cris: Fix conflicting types for _etext, _edata, _end Sergey Senozhatsky
2018-01-11 14:12 ` Sergey Senozhatsky
2018-01-11 14:24 ` Jesper Nilsson
2018-01-12 1:34 ` Sergey Senozhatsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180112013408.GA6419@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=jesper.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=starvik@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox