mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Alexander Clouter <alex@digriz.org.uk>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: Differentiate SheevaPlugs and DockStars on the basis of the memory size.
Date: Fri, 8 Apr 2011 08:24:20 +0100	[thread overview]
Message-ID: <20110408072420.GA27450@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D9E42E1.1060902@ahsoftware.de>

On Fri, Apr 08, 2011 at 01:04:01AM +0200, Alexander Holler wrote:
> Am 08.04.2011 00:08, schrieb Russell King - ARM Linux:
>
>>> Requiring a machine ID and the needed stuff to handle that for a board
>>> which just is using two GPIOs different than another board is why the
>>> ARM tree exploded.
>>
>> You can not be any more wrong than that.
>>
>> The reason the ARM tree exploded is because of the compartmentalized
>> sub-community structure, where the vast majority of (eg) OMAP development
>> is done independently of the (eg) Samsung development.
>>
>> Consequently, there's no attempt to consolidate code between the SoCs,
>> even for basic stuff like 32-bit up-counting timers.  We've ended up with
>> _nine_ implementations of clocksources all doing the same thing in that
>> respect.
>>
>> That's got precisely zilch to do with machine IDs, and your attempt to
>> blame the bloat on machine IDs just shows how misinformed you are.
>
> I had a look at what's going on in the OMAP linux world for more than a  
> year now and I think I've seen a lot of the stuff you are referring to.
>
> And I think one of the reasons that the mess happened is the same I've  
> got trapped in. Why should anyone try to submit patches if he must fear  
> to get caught in some senseless endless discussion about one line.

Because matching against the memory size is _technically_ the wrong thing
to do, as you've already been told.

  reply	other threads:[~2011-04-08  7:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 20:35 [PATCH 0/2] ARM: Unify setup for Marvell SheevaPlugs and Seagate DockStars Alexander Holler
2011-04-06 20:35 ` [PATCH 1/2] ARM: Differentiate SheevaPlugs and DockStars on the basis of the memory size Alexander Holler
2011-04-06 21:44   ` Nicolas Pitre
2011-04-06 22:45     ` Alexander Holler
2011-04-06 23:01       ` Nicolas Pitre
2011-04-06 23:22         ` Alexander Holler
2011-04-07  2:55           ` Nicolas Pitre
2011-04-07  8:55           ` Alexander Clouter
2011-04-07 21:31             ` Alexander Holler
2011-04-07 21:44               ` Alexander Clouter
2011-04-07 21:59                 ` Alexander Holler
2011-04-07 22:08               ` Russell King - ARM Linux
2011-04-07 23:04                 ` Alexander Holler
2011-04-08  7:24                   ` Russell King - ARM Linux [this message]
2011-04-08  8:38                     ` Alexander Holler
2011-04-09  8:29                   ` Bernd Petrovitsch
2011-04-10 18:14                     ` Alexander Holler
2011-04-10 19:29                       ` Alexander Holler
2011-04-06 23:23         ` Eric Cooper
2011-04-06 20:35 ` [PATCH 2/2] ARM: Remove machine type dockstar (use sheevaplug instead) Alexander Holler
2011-04-06 21:02   ` Nicolas Pitre
2011-04-06 21:43     ` Alexander Holler
2011-04-06 22:50 ` [PATCH 0/2] ARM: Unify setup for Marvell SheevaPlugs and Seagate DockStars Nico Erfurth
2011-04-07  9:20   ` Alexander Holler
2011-04-07  9:37     ` Nico Erfurth
2011-04-07  9:44       ` Alexander Holler
2011-04-07 17:39         ` Russell King - ARM Linux
2011-04-08  3:38           ` Alexander Holler

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=20110408072420.GA27450@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=alex@digriz.org.uk \
    --cc=holler@ahsoftware.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®