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: 46dcfc8 (ARM: Update mach-types) removes used machine types
Date: Mon, 22 Aug 2011 14:27:19 +0100	[thread overview]
Message-ID: <20110822132719.GD2287@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201108221516.00540.marek.vasut@gmail.com>

On Mon, Aug 22, 2011 at 03:16:00PM +0200, Marek Vasut wrote:
> On Monday, August 22, 2011 03:01:19 PM Russell King - ARM Linux wrote:
> > For further reading, see:
> > http://lists.arm.linux.org.uk/lurker/message/20110815.085325.ae6ee07d.en.ht
> > ml
> 
> Russell, calm down please.
> 
> Maybe it'd be better to just email the people with broken stuff, then
> wait ... if they don't reply in a week (two weeks?) then remove their
> stuff. And make that a policy.
> 
> What do you think ?

Who do I email?  Which entries are causing problems?  That's the whole
bloody point.

There's just far too much of it.  The amount of effort required to sort
through this file each time it needs to be updated has become *excessive*.
The amount of effort required to go through the file and identify which
entries are broken is *excessive*.  The amount of effort required to
find who to email is *excessive*.

I don't have a few days to do that - and I'm not going to repeat it
every time the file needs to be updated anymore.

So either I drop the change and we go back to having gplugd broken, or
we keep the change and have the Eureka stuff broken.  Anything else is
far too much hastle.

Given that the gplugd folk have sorted out their problems, and its the
Eureka stuff which doesn't conform, I'd rather that Eureka was broken
rather than gplugd.

  reply	other threads:[~2011-08-22 13:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22  8:10 46dcfc8 (ARM: Update mach-types) removes used machine types Uwe Kleine-König
2011-08-22  8:17 ` Russell King - ARM Linux
2011-08-22  8:33   ` Uwe Kleine-König
2011-08-22 11:18     ` Marek Vasut
2011-08-22 12:49       ` Russell King - ARM Linux
2011-08-22 12:54         ` Marek Vasut
2011-08-22 12:56           ` Russell King - ARM Linux
2011-08-22 13:01             ` Russell King - ARM Linux
2011-08-22 13:16               ` Marek Vasut
2011-08-22 13:27                 ` Russell King - ARM Linux [this message]
2011-08-22 13:30                   ` Marek Vasut
2011-08-22 13:32                     ` Russell King - ARM Linux
2011-08-22 13:36                       ` Marek Vasut
2011-08-22 13:48                         ` Russell King - ARM Linux
2011-08-22 14:09                           ` Eric Miao
2011-08-22 13:04             ` Eric Bénard
2011-08-22 13:55               ` Russell King - ARM Linux
2011-08-22 14:19                 ` [PATCH] cpuimx* boards: fix mach-types errors Eric Bénard
2011-08-22 14:37                   ` Russell King - ARM Linux
2011-08-22 14:43                     ` Eric Bénard
2011-08-22 12:55         ` 46dcfc8 (ARM: Update mach-types) removes used machine types Russell King - ARM Linux

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=20110822132719.GD2287@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).