From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Heads up: Linus plans to kill ARM defconfigs
Date: Tue, 8 Jun 2010 14:10:07 +0100 [thread overview]
Message-ID: <20100608131007.GE25370@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4C0E3CAF.4050409@weinigel.se>
On Tue, Jun 08, 2010 at 02:50:55PM +0200, Christer Weinigel wrote:
> Linus isn't stupid. If you explain what you are doing and that the goal
> is to reduce the set of defconfigs to just one per processor family, and
> that it will reduce the churn in the end, I think Linus will listen.
Linus has said in no uncertain terms that all but one or two ARM defconfigs
will be deleted at the next merge window. That's not "one or two defconfigs
per platform class".
> Actually, why not just ask Linus if the the way Ben Dooks has structured
> the Samsung defconfigs would be ok with him. It's only one defconfig
> per CPU family and each defconfig supports a lot of boards.
When you look at what Linus is complaining about in the diffstat, you
realise that the S3C stuff is part of the problem. This is what the
diffstat for arch/arm/configs looks like for the period covering
2.6.34 to 2.6.35-rc1 - which is the one which provoked Linus' reaction.
arch/arm/configs/am3517_evm_defconfig | 144 +++-
arch/arm/configs/ams_delta_defconfig | 10 +-
arch/arm/configs/cns3420vb_defconfig | 831 +++++++++++++
arch/arm/configs/devkit8000_defconfig | 157 ++-
arch/arm/configs/mmp2_defconfig | 75 +-
arch/arm/configs/mx51_defconfig | 17 +-
arch/arm/configs/omap3_defconfig | 151 ++-
arch/arm/configs/omap3_evm_defconfig | 51 +-
arch/arm/configs/omap3_stalker_lks_defconfig | 1691 ++++++++++++++++++++++++++
arch/arm/configs/omap_4430sdp_defconfig | 448 +++++++-
arch/arm/configs/rx51_defconfig | 39 +-
arch/arm/configs/s3c2410_defconfig | 719 ++++++-----
arch/arm/configs/s3c6400_defconfig | 637 +++++++++-
arch/arm/configs/s5p6440_defconfig | 87 +-
arch/arm/configs/s5p6442_defconfig | 66 +-
arch/arm/configs/s5pc100_defconfig | 235 +++-
arch/arm/configs/s5pc110_defconfig | 52 +-
arch/arm/configs/s5pv210_defconfig | 55 +-
arch/arm/configs/spear300_defconfig | 773 ++++++++++++
arch/arm/configs/spear310_defconfig | 775 ++++++++++++
arch/arm/configs/spear320_defconfig | 775 ++++++++++++
arch/arm/configs/spear600_defconfig | 760 ++++++++++++
arch/arm/configs/stamp9g20_defconfig | 1456 ++++++++++++++++++++++
23 files changed, 9323 insertions(+), 681 deletions(-)
Notice that almost a third (7/23) of the files were Samsung related.
It's also not just about the number of defconfigs. Linus had other
valid points too - for example, you can't review the changes to them
properly, because any change to them is far too noisy. That point
doesn't go away by reducing the number of defconfigs.
> s3c2410_defconfig supports most ARM9 based Samsung SoCs, S3C2410,
> S3C2412, S3C2413, S3C2440 and S3C2442, all in all some 20-odd boards. So
> for someone who wants to start a new S3C port they can just use the
> s3c2410_defconfig as a base, which I think is how Linus want's the
> defconfigs to be used.
I think Linus has made up his mind about what he wants to see, and that's
what we have to provide him with. However, if you think you've got a
great alternative, please get involved with the thread on LKML and see if
_you_ can change his mind.
next prev parent reply other threads:[~2010-06-08 13:10 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
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 [this message]
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=20100608131007.GE25370@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).