From: "Jack Stone" <jwjstone@fastmail.fm>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Arm and allyesconfig, allnoconfig, allmodconfig and randconfig
Date: Thu, 30 Apr 2009 14:17:34 +0200 [thread overview]
Message-ID: <1241093854.6754.1313086299@webmail.messagingengine.com> (raw)
In-Reply-To: <20090430083348.GA4313@n2100.arm.linux.org.uk>
On Thu, 30 Apr 2009 09:33 +0100, "Russell King - ARM Linux"
<linux@arm.linux.org.uk> wrote:
> Patches welcome.
Is this the sort of thing you meant? I don't know if the text or
location is correct so comments are very welcome.
Thanks,
Jack
Document that ARM doesn't support all*config
From: Jack Stone <jwjstone@fastmail.fm>
ARM doesn't support all*config. This is because it does not make sense
as
there are so many different variants. Instead the defconfigs should be
used.
Signed-off-by: Jack Stone <jwjstone@fastmail.fm>
---
Documentation/arm/README | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/arm/README b/Documentation/arm/README
index d98783f..8239e5f 100644
--- a/Documentation/arm/README
+++ b/Documentation/arm/README
@@ -36,6 +36,9 @@ Compilation of kernel
(arch/arm/boot/Image). A compressed image can be built by doing a
'make zImage' instead of 'make Image'.
+ NOTE: ARM Linux doesn't support the all*config targets. This is
because of
+ the number of variants supported. The defconfig targets should be
used
+ instead.
Bug reports etc
---------------
prev parent reply other threads:[~2009-04-30 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 8:28 Arm and allyesconfig, allnoconfig, allmodconfig and randconfig Jack Stone
2009-04-30 8:33 ` Russell King - ARM Linux
2009-04-30 12:17 ` Jack Stone [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=1241093854.6754.1313086299@webmail.messagingengine.com \
--to=jwjstone@fastmail.fm \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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