mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Tony Breeds <tony@bakeyournoodle.com>,
	linux-metag@vger.kernel.org,
	Fengguang Wu <fengguang.wu@intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Richard Kuo <rkuo@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Consult] About tool chains of metag
Date: Thu, 05 Dec 2013 18:20:25 +0800	[thread overview]
Message-ID: <52A05369.1090908@gmail.com> (raw)
In-Reply-To: <52A04A5F.9030001@imgtec.com>

On 12/05/2013 05:41 PM, James Hogan wrote:
> On 05/12/13 08:46, Chen Gang wrote:
>> On 12/05/2013 09:57 AM, Chen Gang wrote:
>>> I will/should try my best to let it pass allmodconfig, and I guess
>>> https://lkml.kernel.org/r/201211161520.03974.arnd@arndb.de is valuable
>>> to me, and I will/should reference it.
>>>
>>
>> Oh, excuse me, I can not access "https://lkml.kernel.org/r/..." in
>> normal way in China.  :-(
>>
>> Could you please provide another links which include the same contents?
> 
> http://marc.info/?l=linux-arch&m=135307927916985
> http://article.gmane.org/gmane.linux.kernel.cross-arch/15908
> 

That is really valuable to me!!

You and arnd have done much for HAVE_XXX, and I should continue to try
based on your work. For me, it is really a suitable solution for all
HAVE_XXX (although still need think of more details).  :-)

Welcome another related members to provide your suggestions or completions.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water and life which God blessed

           reply	other threads:[~2013-12-05 10:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <52A04A5F.9030001@imgtec.com>]

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=52A05369.1090908@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=fengguang.wu@intel.com \
    --cc=geert@linux-m68k.org \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=rkuo@codeaurora.org \
    --cc=tony@bakeyournoodle.com \
    --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

Powered by JetHome