All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: james.smart@emulex.com, Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/5] lpfc 10.2.8001.0: Removed obsolete PCI IDs from the driver
Date: Fri, 23 May 2014 17:58:42 +0200	[thread overview]
Message-ID: <537F7032.6060001@suse.de> (raw)
In-Reply-To: <537A41E6.8010607@emulex.com>

On 05/19/2014 07:39 PM, James Smart wrote:
> :)
>
> for those distros, that want to pull only upstream'd patches, and where
> customers expect someone to take phone calls on any hardware recognized
> by the distro... the patch is to remove the hardware Emulex/the distro
> won't answer any questions for anymore.
>
> true - the hardware, if you can find it lying around somewhere, may
> still function. It won't get firmware updates, nor any mindshare. I'm
> not sure where the policy is for upstream - is it truly once known, can
> never be taken away ?
>
Problem is, no-one does.

But I've proposed a micro-conf at LPC in October to discuss exactly
this. You're welcomed to join :-)
It would be good to have a mechanism which would retain the 
functionality, but at the same time indicating that for any errors
you might be on your own.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-05-23 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 15:53 [PATCH 3/5] lpfc 10.2.8001.0: Removed obsolete PCI IDs from the driver James Smart
2014-05-19 17:19 ` Christoph Hellwig
2014-05-19 17:39   ` James Smart
2014-05-19 17:53     ` Christoph Hellwig
2014-05-23 15:58     ` Hannes Reinecke [this message]

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=537F7032.6060001@suse.de \
    --to=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=james.smart@emulex.com \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.