linux-kernel - Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 01 Dec 2011 12:49:58 -0800
From:	Daniel Walker <dwalker@...o99.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
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, 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..

Daniel

--
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/