From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: Heads up: Linus plans to kill ARM defconfigs
Date: Sat, 05 Jun 2010 00:08:44 +0200 [thread overview]
Message-ID: <m38w6ulac3.fsf@intrepid.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1006041418390.22319@xanadu.home> (Nicolas Pitre's message of "Fri, 04 Jun 2010 16:51:24 -0400 (EDT)")
Nicolas Pitre <nico@fluxnic.net> writes:
> Linus wants something to be done about the current defconfig mess which
> is perfectly legitimate. He even suggested a possible solution. I
> don't think he'll simply drop those defconfig files if we demonstrate
> that we're taking action to fix the actual problem.
To be honest, I see no usefulness in current defconfigs. Not only ARM
- in any and all defconfigs altogether.
Having this info somewhere on the web, maybe - just like we have the
build logs etc. But in the kernel source tree?
I wonder if I'm the only one frequently doing
grep CONFIG* ... | grep -v defconfig.
I think the issue will fix itself when the "select problem" is fixed.
And we should've fixed the "select problem" long ago (e.g. Kconfig*
should be able to select things without worrying about intermediate
steps, and it should be able to ask the user if needed).
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-06-04 22:08 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 19:24 Heads up: Linus plans to kill ARM defconfigs Russell King - ARM Linux
2010-06-03 19:55 ` Marek Vasut
2010-06-03 20:01 ` Russell King - ARM Linux
2010-06-03 20:27 ` Marek Vasut
2010-06-03 20:38 ` Nicolas Pitre
2010-06-08 14:41 ` Russell King - ARM Linux
2010-06-03 23:46 ` Daniel Walker
2010-06-04 11:06 ` Uwe Kleine-König
2010-06-03 19:59 ` Nicolas Pitre
2010-06-03 20:03 ` Russell King - ARM Linux
2010-06-03 20:36 ` Nicolas Pitre
2010-06-03 21:04 ` Ryan Mallon
2010-06-03 22:31 ` Nicolas Pitre
2010-06-03 23:33 ` Ryan Mallon
2010-06-03 23:45 ` Kyungmin Park
2010-06-04 0:13 ` Nicolas Pitre
2010-06-04 1:10 ` Marek Vasut
2010-06-04 1:16 ` Ryan Mallon
2010-06-04 1:35 ` Eric Miao
2010-06-04 1:37 ` Marek Vasut
2010-06-04 1:50 ` Marek Vasut
2010-06-04 1:53 ` Marek Vasut
2010-06-04 6:03 ` Tony Lindgren
2010-06-04 14:59 ` Cory Maccarrone
2010-06-07 7:41 ` Tony Lindgren
2010-06-04 1:57 ` Eric Miao
2010-06-04 6:10 ` Tony Lindgren
2010-06-04 7:12 ` Eric Miao
2010-06-04 8:40 ` Martin Guy
2010-06-04 20:51 ` Nicolas Pitre
2010-06-04 22:08 ` Krzysztof Halasa [this message]
2010-06-08 11:58 ` Russell King - ARM Linux
2010-06-08 12:31 ` Tony Lindgren
2010-06-08 12:43 ` Eric Miao
2010-06-08 12:49 ` Russell King - ARM Linux
2010-06-08 13:00 ` Eric Miao
2010-06-08 12:43 ` David John
2010-06-08 12:44 ` Eric Miao
2010-06-08 12:50 ` Nicolas Pitre
2010-06-08 12:44 ` Nicolas Pitre
2010-06-08 12:50 ` Russell King - ARM Linux
2010-06-08 13:01 ` Nicolas Pitre
2010-06-08 13:13 ` Russell King - ARM Linux
2010-06-08 14:51 ` Eric Miao
2010-06-08 16:55 ` Nicolas Pitre
2010-06-08 23:23 ` Daniel Walker
2010-06-08 12:50 ` Christer Weinigel
2010-06-08 13:10 ` Russell King - ARM Linux
2010-06-08 20:51 ` Ryan Mallon
2010-06-08 21:22 ` Russell King - ARM Linux
2010-06-08 21:32 ` Ryan Mallon
2010-06-08 23:02 ` Nicolas Pitre
2010-06-08 23:21 ` Ryan Mallon
2010-06-08 23:26 ` Daniel Walker
2010-06-08 23:31 ` Nicolas Pitre
2010-06-08 23:52 ` Ryan Mallon
2010-06-09 0:14 ` Nicolas Pitre
2010-06-09 6:07 ` Hendrik Sattler
2010-06-09 13:32 ` Daniel Walker
2010-06-10 6:32 ` Uwe Kleine-König
2010-06-10 19:18 ` Nicolas Pitre
2010-06-09 21:56 ` Ryan Mallon
2010-06-25 12:36 ` Catalin Marinas
2010-06-07 21:09 ` Ryan Mallon
2010-06-04 10:42 ` Tony Lindgren
2010-06-04 8:36 ` pieterg
[not found] ` <AANLkTilyIb8WDAanNHlQKHco6rSjzNjNS9Q3TpWQqt8o@mail.gmail.com>
2010-06-04 8:42 ` Eric Miao
2010-06-04 8:56 ` Daniel Mack
2010-06-04 9:37 ` pieterg
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=m38w6ulac3.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--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.