From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Cc: Don Brace <don.brace@microsemi.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Meelis Roos <mroos@linux.ee>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH RESEND 0/6] hpsa: support legacy boards
Date: Thu, 10 Aug 2017 07:06:53 -0700 [thread overview]
Message-ID: <1502374013.2736.11.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170810070904.GA20910@lst.de>
On Thu, 2017-08-10 at 09:09 +0200, Christoph Hellwig wrote:
> No device support in Linux is unsupported, sorry. I think we're
> getting into the corporate bullshit game a little too much here.
I think there are two different definitions of supported here. To us,
any device to which the driver attaches is "supported". However, if
it's never been tested before it may not work very well. In the Linux
way, we'll try to fix the bugs when they're reported and in that sense
we support the device until nothing in the kernel attaches to its ids
anymore.
In the corporate world "supported" means we'll sell you a contract
giving you certain rights to report bugs and have us fix them. There
are definite reasons why corporations only support a small range of new
devices, even though devices not on this list may still be attached to
by the driver and thus we (Linux Community) would try to fix the bug
reports for.
I think what you're basically asking for is a different name for the
flag, which is fine? how about 'legacy' instead?
James
next prev parent reply other threads:[~2017-08-10 14:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 8:35 [PATCH RESEND 0/6] hpsa: support legacy boards Hannes Reinecke
2017-08-08 8:35 ` [PATCH 1/6] hpsa: consolidate status variables Hannes Reinecke
2017-08-09 13:40 ` Christoph Hellwig
2017-08-14 10:02 ` Hannes Reinecke
2017-08-08 8:35 ` [PATCH 2/6] hpsa: add support for legacy boards Hannes Reinecke
2017-08-09 13:41 ` Christoph Hellwig
2017-08-09 15:08 ` Hannes Reinecke
2017-08-09 15:59 ` Christoph Hellwig
2017-08-09 13:45 ` Christoph Hellwig
2017-08-09 14:50 ` Hannes Reinecke
2017-08-08 8:35 ` [PATCH 3/6] hpsa: disable volume status check for older controller Hannes Reinecke
2017-08-09 13:42 ` Christoph Hellwig
2017-08-11 13:23 ` Tomas Henzl
2017-08-14 10:45 ` Hannes Reinecke
2017-08-08 8:35 ` [PATCH 4/6] hpsa: Ignore errors for unsupported LV_DEVICE_ID VPD page Hannes Reinecke
2017-08-09 13:45 ` Christoph Hellwig
2017-08-08 8:35 ` [PATCH 5/6] hpsa: do not print errors for unsupported report luns format Hannes Reinecke
2017-08-09 13:46 ` Christoph Hellwig
2017-08-09 14:52 ` Hannes Reinecke
2017-08-08 8:35 ` [PATCH 6/6] hpsa: handle unsupported devices more gracefully Hannes Reinecke
2017-08-09 13:48 ` Christoph Hellwig
2017-08-09 22:08 ` [PATCH RESEND 0/6] hpsa: support legacy boards Don Brace
2017-08-10 7:07 ` Hannes Reinecke
2017-08-10 7:09 ` Christoph Hellwig
2017-08-10 7:29 ` Hannes Reinecke
2017-08-10 14:06 ` James Bottomley [this message]
2017-08-10 14:11 ` Hannes Reinecke
2017-08-10 19:15 ` Don Brace
2017-08-11 6:43 ` Hannes Reinecke
2017-08-11 16:35 ` Don Brace
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=1502374013.2736.11.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=don.brace@microsemi.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mroos@linux.ee \
/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).