From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Walker <dwalker@fifo99.com>
Cc: David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support
Date: Thu, 1 Dec 2011 21:03:32 +0000 [thread overview]
Message-ID: <20111201210332.GI9581@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1322772598.3704.33.camel@m0nster>
On Thu, Dec 01, 2011 at 12:49:58PM -0800, Daniel Walker wrote:
> On Thu, 2011-12-01 at 20:35 +0000, Russell King - ARM Linux wrote:
> > 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?
>
> Yeah I did notice..
>
> > 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.
>
> I agree with the steps, but I'm not sure David knows about (or would be
> following) those steps. Not to mention these devices are still readily
> available used .. I wouldn't expect anyone to even remotely ponder
> removing this code for at least another 10 years.. In order to even
> start the process above there has to be some good probability that no
> has the device or cares at all about the device..
Actually... no. We've removed entire SoCs which have lost their
maintainers well under this '10 years'.
One of the key decisions for removing code is the cost of keeping it
in a buildable state when there's no one actively looking after it.
If it has a high cost it'll get deleted much earlier...
next prev parent reply other threads:[~2011-12-01 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 0:29 [PATCH 1/3] ARM: msm: Remove MSM7x00 support David Brown
2011-12-01 0:29 ` [PATCH 2/3] gpio_msm: remove support for MSM7x01 David Brown
2011-12-01 0:29 ` [PATCH 3/3] ARM: msm: Remove cpu_is test for msm7201 soc David Brown
2011-12-01 15:17 ` [PATCH 1/3] ARM: msm: Remove MSM7x00 support Daniel Walker
2011-12-01 18:17 ` David Brown
2011-12-01 18:39 ` Daniel Walker
2011-12-01 19:27 ` David Brown
2011-12-01 19:33 ` Daniel Walker
2011-12-01 19:43 ` David Brown
2011-12-01 19:53 ` Daniel Walker
2011-12-01 20:17 ` David Brown
2011-12-01 20:19 ` Russell King - ARM Linux
2011-12-01 20:25 ` Daniel Walker
2011-12-01 20:35 ` Russell King - ARM Linux
2011-12-01 20:49 ` Daniel Walker
2011-12-01 21:03 ` Russell King - ARM Linux [this message]
2011-12-01 21:34 ` Daniel Walker
2011-12-01 20:26 ` David Brown
2011-12-01 20:32 ` Daniel Walker
2011-12-02 13:17 ` Denis 'GNUtoo' Carikli
2011-12-02 15:26 ` David Brown
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=20111201210332.GI9581@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).