From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Steve Kenton <skenton@ou.edu>
Cc: rth@twiddle.net, spyro@f2s.com, bjornw@axis.com,
ysato@users.sourceforge.jp,
Linux Kernel <linux-kernel@vger.kernel.org>,
davidm@hpl.hp.com, jes@trained-monkey.org, ralf@gnu.org,
matthew@wil.cx, paulus@samba.org, schwidefsky@de.ibm.com,
gniibe@m17n.org, wesolows@foobazco.org, davem@redhat.com,
jdike@karaya.com, uclinux-v850@lsi.nec.co.jp, ak@suse.de
Subject: Re: 2.6.2 make defconfig for all arches give 171 "trying to assign nonexistent symbol" errors
Date: Thu, 5 Feb 2004 08:28:29 +0000 [thread overview]
Message-ID: <20040205082828.A4252@flint.arm.linux.org.uk> (raw)
In-Reply-To: <40216DEE.6040306@ou.edu>; from skenton@ou.edu on Wed, Feb 04, 2004 at 04:10:54PM -0600
On Wed, Feb 04, 2004 at 04:10:54PM -0600, Steve Kenton wrote:
> 2.6.2 make defconfig for all arches give 171 "trying to assign nonexistent symbol" errors
> total in 13 different arches, up from 143 in 2.6.1.
>
> arm 37
The standard ARM defconfig is next to useless anyway - most if not all
people will choose one of the other defconfig files in arch/arm/configs
first.
If someone wants to maintain the 46 ARM defconfigs, that's fine by me.
However, traditionally this has ended up producing stupidly massive
patches.
(I'm not saying its a bad thing - I'm just pointing out that keeping
them up to date will be a large job for someone.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-02-05 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 22:10 Steve Kenton
2004-02-04 22:29 ` Matthew Wilcox
2004-02-05 8:28 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 16:56 Steve Kenton
2004-02-04 19:47 ` Sam Ravnborg
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=20040205082828.A4252@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=ak@suse.de \
--cc=bjornw@axis.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=gniibe@m17n.org \
--cc=jdike@karaya.com \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulus@samba.org \
--cc=ralf@gnu.org \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=skenton@ou.edu \
--cc=spyro@f2s.com \
--cc=uclinux-v850@lsi.nec.co.jp \
--cc=wesolows@foobazco.org \
--cc=ysato@users.sourceforge.jp \
/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