[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111201203506.GG9581@n2100.arm.linux.org.uk>
Date: Thu, 1 Dec 2011 20:35:06 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Daniel Walker <dwalker@...o99.com>
Cc: David Brown <davidb@...eaurora.org>,
Bryan Huntsman <bryanh@...eaurora.org>,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support
On Thu, Dec 01, 2011 at 12:25:47PM -0800, Daniel Walker wrote:
> On Thu, 2011-12-01 at 20:19 +0000, Russell King - ARM Linux wrote:
> > Now, the obvious question to ask now is this: as you sent your question,
> > and Daniel obviously objects, was Daniel one of your respondants? If
> > not, then he carries some of the blame for this patch being created
> > in the first place by having missed the email/not replied/etc.
> >
>
> What if the people using the hardware aren't even on the list ? It's not
> their fault is it?
Did you notice I mentioned six months?
The way to remove non-broken code is:
1. to ask. If no one responds, then
2. submit a patch to put an entry in feature-removal-schedule.txt giving a
description of what will be removed and when - and then flag it
with a patch to remove it. If no one responds to that, then
3. the patch to remove it re-posted, and if no one objects it gets
merged.
So, if people care about bits of code _and_ they're not on the relevant
subsystem mailing lists, they need to keep an eye on the feature removal
file - otherwise they're in for nasty surprises.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists