From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acornscsi: remove linked command support
Date: Sat, 24 May 2014 16:13:37 +0400 [thread overview]
Message-ID: <1400933617.6956.34.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <538075E0.4080001@suse.de>
On Sat, 2014-05-24 at 12:35 +0200, Hannes Reinecke wrote:
[...]
> I'm all for it. Removing never-really-implemented feature on obsolete
> hardware is always a good idea.
>
> Acked-by: Hannes Reinecke <hare@suse.de>
Wait, no, that's not a good idea. We leave obsolete drivers to bitrot.
Particularly we try not to touch them unless we have to because there
might be a few people still using them and the more we tamper, the
greater the risk that something gets broken. On that principle, since
there's no real reason to remove the code, it should stay ... until the
whole driver bitrots to the extent that we can no-longer compile it.
However, I'll do this if the Maintainer (rmk) acks ... because if it
breaks he gets to fix it.
James
next prev parent reply other threads:[~2014-05-24 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 10:13 Paul Bolle
2014-05-24 10:35 ` Hannes Reinecke
2014-05-24 12:13 ` James Bottomley [this message]
2014-05-24 13:16 ` Paul Bolle
2014-05-25 7:42 ` James Bottomley
2014-05-28 17:28 ` Paul Bolle
2014-05-28 10:41 ` Christoph Hellwig
2014-05-28 14:26 ` James Bottomley
2014-05-28 15:17 ` 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=1400933617.6956.34.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=hare@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pebolle@tiscali.nl \
/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®