From: Mike Christie <michaelc@cs.wisc.edu>
To: Jayamohan Kalickal <jayamohank@serverengines.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] be2iscsi: Enabling MSIX and mcc_rings
Date: Tue, 13 Oct 2009 17:45:04 -0500 [thread overview]
Message-ID: <4AD502F0.8060600@cs.wisc.edu> (raw)
In-Reply-To: <20091013041956.0f8048d8@mailhost.serverengines.com>
On 10/12/2009 11:19 PM, Jayamohan Kalickal wrote:
> I have put in that code as infrastructure needed when we implement
> the blob that we had discussed. Yes, it needs the changes in scsi_transport_iscsi
> ,then, I will call the mgmt_fw_cmd
>
Ah ok. You will not want to include it with this patch then. Include the
mgmt stuff when you are sending the other code.
next prev parent reply other threads:[~2009-10-13 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 4:19 [PATCH 1/1] be2iscsi: Enabling MSIX and mcc_rings Jayamohan Kalickal
2009-10-13 22:45 ` Mike Christie [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-13 2:52 Jayamohan Kallickal
2009-10-13 3:12 ` Mike Christie
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=4AD502F0.8060600@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=jayamohank@serverengines.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 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).