From: Joe Eykholt <fcoe@eykholt.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [OpenFCoE PATCH] If expecting pre-T11 frames, a T11 frame caused a data fault.
Date: Wed, 05 Dec 2007 08:42:01 -0800 [thread overview]
Message-ID: <4756D4D9.70608@eykholt.com> (raw)
In-Reply-To: <20071205135543.GA2174@infradead.org>
Christoph Hellwig wrote:
> Just wondering:
>
>>From my quick reading of the code these pre-T11 frames are basically
> a different frame-level protocol. Given that T11 has standardized
> on a different one what's the rationale for supporting the old frames?
There is still some use in lab environments of the old frame format, and
it would greatly help if we could keep it working for now. Eventually,
in a year or so, it could be removed completely. It seems to be a small
amount of code and in a loadable module besides.
Joe
prev parent reply other threads:[~2007-12-05 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 0:52 [OpenFCoE PATCH] If expecting pre-T11 frames, a T11 frame caused a data fault Joe Eykholt
2007-12-05 13:55 ` Christoph Hellwig
2007-12-05 16:42 ` Joe Eykholt [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=4756D4D9.70608@eykholt.com \
--to=fcoe@eykholt.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