mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Gang <xili_gchen_5257@hotmail.com>
To: Richard Weinberger <richard@nod.at>,
	Richard Weinberger <richard.weinberger@gmail.com>
Cc: realmz6@gmail.com,
	"adi-buildroot-devel@lists.sourceforge.net" 
	<adi-buildroot-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blackfin: Makefile: Add -D__linux__ flag for KBUILD_CFLAGS
Date: Sun, 5 Apr 2015 05:29:40 +0800	[thread overview]
Message-ID: <BLU436-SMTP16352FB2C5AE4B224F9D32DB9F00@phx.gbl> (raw)
In-Reply-To: <552054DF.4090604@nod.at>

On 4/5/15 05:17, Richard Weinberger wrote:
> Am 04.04.2015 um 23:13 schrieb Chen Gang:
>> Is what I have done above correct? Or can we treate it as gcc's issue?
> 
> At least ask gcc folks about that before you add a random hack to the kernel.
> 

For the latest compiler, it should contents -D__linux__, and what I have
done for building gcc/binutils is the common way, so I guess binutils or
gcc need improvement (I shall try to fix it within this month).

But, I am not quite sure whether the old version bfin compilers also
supports -D__linux__ (comparing some of the old compilers of the other
archs, I guess not). Are you sure the old version bfin compilers are OK?


BTW, for the latest bfin compiler from upstream, it contents another
issues which I bypassed now. I shall try to fix them within this month
(try to send all fix patches v1 within 2015-04-20).


Thanks.
-- 
Chen Gang

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

      reply	other threads:[~2015-04-04 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 20:19 Chen Gang
2015-04-03 22:56 ` Richard Weinberger
2015-04-04 21:13   ` Chen Gang
2015-04-04 21:17     ` Richard Weinberger
2015-04-04 21:29       ` Chen Gang [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=BLU436-SMTP16352FB2C5AE4B224F9D32DB9F00@phx.gbl \
    --to=xili_gchen_5257@hotmail.com \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=realmz6@gmail.com \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.at \
    /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

all inboxes | Powered by JetHome®