From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pcontrol_g20_defconfig should not specify toolchain path
Date: Wed, 7 Dec 2011 04:19:07 +0100 [thread overview]
Message-ID: <20111207031907.GF32515@game.jcrosoft.org> (raw)
In-Reply-To: <1323223937-14281-1-git-send-email-paul.gortmaker@windriver.com>
On 21:12 Tue 06 Dec , Paul Gortmaker wrote:
> Building defconfigs is a routine operation for people checking
> code that touches multiple arch. But this defconfig calls out
> a path to a toolchain that most people will never have.
>
> The defconfigs should not be calling out site specific toolchain
> locations, so delete the setting of CROSS_COMPILE.
>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
simply drop this defconfig is not maintain
now we have soc defconfig
Best Regards,
J.
next prev parent reply other threads:[~2011-12-07 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 2:12 [PATCH] ARM: pcontrol_g20_defconfig should not specify toolchain path Paul Gortmaker
2011-12-07 3:19 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-12-07 3:26 ` Paul Gortmaker
2011-12-07 10:39 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-08 1:47 ` [PATCH] ARM: delete the pcontrol_g20_defconfig Paul Gortmaker
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=20111207031907.GF32515@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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.