From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] Latest randconfig build errors for Head.S
Date: Fri, 15 Mar 2013 18:36:14 +0800 [thread overview]
Message-ID: <5142F99E.6030607@asianux.com> (raw)
In-Reply-To: <CAAQYJAvXLV38shKncAKKqgQ9G0SnXjh+=aJHBdhd29yzVtL80A@mail.gmail.com>
? 2013?03?15? 17:31, Andrea Adami ??:
> AFAIK Arnd is aware and waiting for feedback about his patch:
>
> ARM: compressed/head.S: work around new binutils warning Arnd Bergmann
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/144846.html
excuse me, I am not familiar with arm assemble code, so can not give more information
but at least for me, it seems your patch is more precious, and also welcomed by compiler.
and I don't think your patch make the code "a more complex":
the reason is:
"keeping code simple and clear" is for readers and debuggers, not for writers.
I prefer to write more code to let readers and debuggers easy understand.
(if it has minor negative effect with performance)
thanks.
--
Chen Gang
Asianux Corporation
WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen@asianux.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
matthew.leach@arm.com, dave.martin@linaro.org, nico@linaro.org,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Suggestion] Latest randconfig build errors for Head.S
Date: Fri, 15 Mar 2013 18:36:14 +0800 [thread overview]
Message-ID: <5142F99E.6030607@asianux.com> (raw)
In-Reply-To: <CAAQYJAvXLV38shKncAKKqgQ9G0SnXjh+=aJHBdhd29yzVtL80A@mail.gmail.com>
于 2013年03月15日 17:31, Andrea Adami 写道:
> AFAIK Arnd is aware and waiting for feedback about his patch:
>
> ARM: compressed/head.S: work around new binutils warning Arnd Bergmann
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/144846.html
excuse me, I am not familiar with arm assemble code, so can not give more information
but at least for me, it seems your patch is more precious, and also welcomed by compiler.
and I don't think your patch make the code "a more complex":
the reason is:
"keeping code simple and clear" is for readers and debuggers, not for writers.
I prefer to write more code to let readers and debuggers easy understand.
(if it has minor negative effect with performance)
thanks.
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-03-15 10:36 UTC|newest]
Thread overview: 18+ 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 4:38 ` Chen Gang
2013-03-14 23:43 ` Russell King - ARM Linux
2013-03-14 23:43 ` Russell King - ARM Linux
2013-03-15 0:52 ` Chen Gang
2013-03-15 0:52 ` Chen Gang
2013-03-15 9:31 ` Andrea Adami
2013-03-15 9:31 ` Andrea Adami
2013-03-15 10:36 ` Chen Gang [this message]
2013-03-15 10:36 ` Chen Gang
2013-03-15 10:56 ` Arnd Bergmann
2013-03-15 10:56 ` Arnd Bergmann
2013-03-15 11:11 ` Chen Gang F T
2013-03-15 11:11 ` Chen Gang F T
2013-03-15 11:29 ` Arnd Bergmann
2013-03-15 11:29 ` Arnd Bergmann
2013-03-17 2:31 ` Chen Gang F T
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=5142F99E.6030607@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.