public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Chen Gang <xili_gchen_5257@hotmail.com>, realmz6@gmail.com
Cc: adi-buildroot-devel@lists.sourceforge.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST enabled
Date: Thu, 09 Apr 2015 15:38:25 +0200	[thread overview]
Message-ID: <552680D1.8020301@nod.at> (raw)
In-Reply-To: <BLU436-SMTP19994F8205B93A483B05312B9FB0@phx.gbl>

Am 09.04.2015 um 15:28 schrieb Chen Gang:
> On 4/9/15 05:12, Richard Weinberger wrote:
>> Am 08.04.2015 um 23:10 schrieb Chen Gang:
>>>
>>> After this patch, blackfin can pass allmodconfig building (if we treat
>>> it as allmodconfig). And next, I shall try to:
>>>
>>>  - Send all related patches v2 for blackfin kernel within this month.
>>>
>>>  - Fix blackfin gcc/binutils related issues within this month.
>>
>> All you do is randomly papering over issues to make the allmodconfig build
>> somehow proceed.
>> This is not the correct way to deal with problems.
>>
> 
> Still, for me, it is not a good idea to make a conclusion in discussing.
> 
> For gcc/binutils issues, they are real world issue, they need to be
> fixed, next (I shall try to fix them within this month).

I leave that up to the blackfin maintainer.
IMHO this is wrong, you're not fixing a real world issue, all you do is
making allmodconfig somehow proceed by papering over possible real issues
which you cannot test as you don't have blackfin hardware.

Thanks,
//richard

  reply	other threads:[~2015-04-09 13:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 21:03 [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST enabled Chen Gang
2015-04-08 21:10 ` Chen Gang
2015-04-08 21:12   ` Richard Weinberger
2015-04-09 13:28     ` Chen Gang
2015-04-09 13:38       ` Richard Weinberger [this message]
2015-04-09 23:14         ` Chen Gang
2015-04-22  9:00 ` Steven Miao
2015-04-22 14:32   ` Chen Gang
2015-04-23  2:51     ` Steven Miao
2015-04-23 14:30       ` Chen Gang
2015-04-24  8:20         ` Steven Miao
2015-04-24 14:28           ` Chen Gang
     [not found] ` <5525994D.6090901@hotmail.com>
2015-07-01 15:31   ` Chen Gang
2015-07-01 15:36   ` Chen Gang
  -- strict thread matches above, loose matches on Subject: below --
2015-04-08 21:05 Chen Gang
2015-04-08 21:10 ` Richard Weinberger
2015-04-08 21:16   ` Chen Gang
2015-04-08 21:19     ` Richard Weinberger
2015-04-09 13:15       ` Chen Gang
2015-04-08 21:05 Chen Gang
2015-04-08 21:07 Chen Gang

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=552680D1.8020301@nod.at \
    --to=richard@nod.at \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=realmz6@gmail.com \
    --cc=xili_gchen_5257@hotmail.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