linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM defconfig files
Date: Mon, 12 Jul 2010 21:06:04 +0100	[thread overview]
Message-ID: <20100712200604.GD9897@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTinxUqzxClVDTyruJ6kzFTganXUGJJHJ5wRi9Iak@mail.gmail.com>

On Mon, Jul 12, 2010 at 10:40:36AM -0700, Linus Torvalds wrote:
> On Mon, Jul 12, 2010 at 10:32 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >
> > When you brought up the problem you seemed absolutely convinced
> > that nothing except your solution was going to be acceptable.
> 
> That's not true. What's true is that you didn't seem to _understand_
> my solution, so I tried to push the understanding of it.

That's your point of view.

My viewpoint was that I had read your email, thought of some alternative
solution, proposed it and the result was shot down without any apparant
thought about it.  That gave the impression that you _only_ wanted to
see your own solution.

The result of that has been very little in the way of progress towards
either your, or my alternative solutions - and apart from a few Kconfig
corner quirk patches, the only major work that's happened has been from
Uwe.

So in that regard, I support Uwe's patches as a means to prevent the
impending loss of build coverage from facilities such as linux-next and
the ARM kernel autobuilder, as that's the only option that's currently
available.

As far as timing goes, I see no reason for it to be merged during -rc.
As has already been said, I'm intending _not_ to make the defconfig
situation any worse by accepting patches which add to the mess, as I'm
also mindful that its exactly those kinds of patches are the cause of
this problem.

Now, I'm happy to take Uwe's tree through mine for the next merge
window _iff_ you find his solution acceptable, and you want that to
happen.

I'll also use this opportunity to warn you now - especially as you also
complained about the amount of churn.  There is an effort to try to
allow a single ARM kernel to boot on a wider range of platforms with
more differences than it currently does.  This is going to mean a
certain amount of restructuring, and a lot of additional patches over
time to gradually convert the code.  So, I'm expecting that there will
be even _more_ patches - some fairly big - to come over the next year
or so.

To give an idea - if we change the structure which defines a machine's
properties, we're going to be changing 348 files under arch/arm to match.
Clearly that's also going to give you a problem with diffstat being
swamped.

  parent reply	other threads:[~2010-07-12 20:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100603074548.GA12104@flint.arm.linux.org.uk>
     [not found] ` <alpine.LFD.2.00.1006030725420.8175@i5.linux-foundation.org>
     [not found]   ` <20100603181010.GA25779@flint.arm.linux.org.uk>
     [not found]     ` <1275589230.23384.19.camel@c-dwalke-linux.qualcomm.com>
     [not found]       ` <alpine.LFD.2.00.1006031119440.8175@i5.linux-foundation.org>
2010-06-14  8:32         ` ARM defconfig files Uwe Kleine-König
2010-06-30 10:40           ` Uwe Kleine-König
2010-07-12 15:55             ` Uwe Kleine-König
2010-07-12 16:51               ` Linus Torvalds
2010-07-12 17:32                 ` Russell King - ARM Linux
2010-07-12 17:40                   ` Linus Torvalds
2010-07-12 18:50                     ` Uwe Kleine-König
2010-07-12 19:04                       ` Linus Torvalds
2010-07-12 19:17                         ` Nicolas Pitre
2010-07-12 19:34                           ` Linus Torvalds
2010-07-12 19:50                             ` Grant Likely
2010-07-13  7:07                               ` Uwe Kleine-König
2010-07-13  8:07                                 ` optimized script [Was: ARM defconfig files] Uwe Kleine-König
2010-07-13 18:04                                   ` Olof Johansson
2010-07-13 23:39                                     ` Nicolas Pitre
2010-07-13 18:32                                 ` ARM defconfig files Grant Likely
2010-07-12 19:59                             ` Uwe Kleine-König
2010-07-12 20:14                             ` Nicolas Pitre
2010-07-12 19:09                       ` Nicolas Pitre
2010-07-12 20:31                       ` Arnd Bergmann
2010-07-12 20:50                         ` Nicolas Pitre
2010-07-12 23:05                       ` David Brown
2010-07-12 23:18                         ` Linus Torvalds
2010-07-12 23:34                           ` David Brown
2010-07-13  0:55                             ` Nicolas Pitre
2010-07-14  9:13                             ` Felipe Contreras
2010-07-14 13:20                             ` Uwe Kleine-König
2010-07-14 17:37                               ` Tony Luck
2010-07-13 18:32                           ` Rob Landley
2010-07-12 20:06                     ` Russell King - ARM Linux [this message]
2010-07-12 20:29                       ` Nicolas Pitre
2010-07-12 21:54                         ` Linus Torvalds
2010-07-14  9:21                       ` Felipe Contreras

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=20100712200604.GD9897@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).