From: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Andrea Adami <andrea.adami@gmail.com>,
Chen Gang <gang.chen@asianux.com>,
matthew.leach@arm.com, dave.martin@linaro.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
nico@linaro.org, Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
matthew.gretton-dann@linaro.org
Subject: Re: [Suggestion] Latest randconfig build errors for Head.S
Date: Fri, 15 Mar 2013 19:11:36 +0800 [thread overview]
Message-ID: <514301E8.9040201@gmail.com> (raw)
In-Reply-To: <201303151056.55819.arnd@arndb.de>
于 2013年03月15日 18:56, Arnd Bergmann 写道:
> Right. The fact that as prints a warning for those instructions makes sense
> given that we are telling it we want to run on *all* ARM architectures,
> and that ARMv8 has deprecated them officially.
>
> Of course, what is bogus about this is the "NULL" part rather than printing
> the text that was meant to come out to explain the situation. I don't
> know how to report that bug other than what I tried before, but if it gets
> fixed by printing the right text, we will still want to build a kernel
> without getting any warnings.
excuse me, my English is not quite well.
I guess your meaning is:
"that bug" means the toolchain's bug (need toolchain people fix it).
prefer to apply your patch, before "that bug" is fixed (we don't know when)
is it correct ?
thanks.
--
Chen Gang
Flying Transformer
next prev parent reply other threads:[~2013-03-15 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 4:38 [Suggestion] Latest randconfig build errors for Head.S Chen Gang
2013-03-14 23:43 ` Russell King - ARM Linux
2013-03-15 0:52 ` Chen Gang
2013-03-15 9:31 ` Andrea Adami
2013-03-15 10:36 ` Chen Gang
2013-03-15 10:56 ` Arnd Bergmann
2013-03-15 11:11 ` Chen Gang F T [this message]
2013-03-15 11:29 ` Arnd Bergmann
2013-03-17 2:31 ` Chen Gang F T
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=514301E8.9040201@gmail.com \
--to=chen.gang.flying.transformer@gmail.com \
--cc=andrea.adami@gmail.com \
--cc=arnd@arndb.de \
--cc=dave.martin@linaro.org \
--cc=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matthew.gretton-dann@linaro.org \
--cc=matthew.leach@arm.com \
--cc=nico@linaro.org \
--cc=will.deacon@arm.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