From: James Smart <james.smart@emulex.com>
To: 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: Mon, 19 May 2014 13:39:50 -0400 [thread overview]
Message-ID: <537A41E6.8010607@emulex.com> (raw)
In-Reply-To: <20140519171944.GC32250@infradead.org>
:)
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 ?
-- james s
On 5/19/2014 1:19 PM, Christoph Hellwig wrote:
> On Mon, May 12, 2014 at 11:53:27AM -0400, James Smart wrote:
>> Removed obsolete PCI IDs from the driver.
> How are these obsolete?
>
>
>
next prev parent reply other threads:[~2014-05-19 17:39 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 [this message]
2014-05-19 17:53 ` Christoph Hellwig
2014-05-23 15:58 ` Hannes Reinecke
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=537A41E6.8010607@emulex.com \
--to=james.smart@emulex.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox