From: Hannes Reinecke <hare@suse.de>
To: Praveen Madhavan <praveenm@chelsio.com>,
David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
JBottomley@parallels.com, hch@infradead.org,
hariprasad@chelsio.com, varun@chelsio.com
Subject: Re: [PATCH 0/2] Remove T4 FCoE support
Date: Fri, 16 Jan 2015 08:19:41 +0100 [thread overview]
Message-ID: <54B8BB8D.8050602@suse.de> (raw)
In-Reply-To: <20150116042616.GA1264@fcoe-test11>
On 01/16/2015 05:32 AM, Praveen Madhavan wrote:
> On Thu, Jan 15, 2015 at 02:04:53PM -0500, David Miller wrote:
>> From: Praveen Madhavan <praveenm@chelsio.com>
>> Date: Thu, 15 Jan 2015 19:15:50 +0530
>>
>>> These patches removes FCoE support for chelsio T4 adapter.
>>> Please apply on net-next since depends on previous commits.
>>
>> Why is it being removed? You have to state this in the
>> commit log messages at a minimum.
>>
> We found a subtle issue with FCoE on T4 very late in the game
> and decided not to productize FCoE on T4 and therefore there
> are no customers that will be impacted by this change. FCoE is
> supported on T5 cards.
> Sorry about that, not mentioning in commit log. Can i resend this
> patch with updated commit log?
>
Yes, please do.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (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
prev parent reply other threads:[~2015-01-16 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 13:45 [PATCH 0/2] Remove T4 FCoE support Praveen Madhavan
2015-01-15 13:45 ` [PATCH 1/2] csiostor:Remove " Praveen Madhavan
2015-01-15 13:45 ` [PATCH 2/2] csiostor:Removed file csio_hw_t4.c Praveen Madhavan
2015-01-15 14:25 ` [PATCH 0/2] Remove T4 FCoE support Hannes Reinecke
2015-01-15 19:04 ` David Miller
2015-01-16 4:32 ` Praveen Madhavan
2015-01-16 7:19 ` 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=54B8BB8D.8050602@suse.de \
--to=hare@suse.de \
--cc=JBottomley@parallels.com \
--cc=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=praveenm@chelsio.com \
--cc=varun@chelsio.com \
/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).