From: Mike Christie <michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
To: open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
anilgv-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
benli-dY08KVG/lbpWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH 0/4] Add bnx2i driver.
Date: Tue, 26 May 2009 21:35:50 -0500 [thread overview]
Message-ID: <4A1CA706.1020108@cs.wisc.edu> (raw)
In-Reply-To: <1243113110-29635-1-git-send-email-mchan-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Michael Chan wrote:
>
> James, the next 4 patches are our latest to add the bnx2i
> driver. We've fixed up all the issues that Mike brought up.
> Please consider applying them to scsi-misc-2.6.
>
Hey James,
We forgot to cc you and the linux list on some other postings. Dave
Miller had ackd the drivers/net parts of the patches here:
http://marc.info/?l=linux-netdev&m=124082705613349&w=2
and in the mail had said it was ok to send through the scsi tree.
There is just some tiny comment issue in one of the patches that I think
is probably ok to fix up after the merge into scsi-misc. A code snippet
got commented out when it should have got removed.
prev parent reply other threads:[~2009-05-27 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 21:11 [PATCH 0/4] Add bnx2i driver Michael Chan
2009-05-23 21:11 ` [PATCH 1/4] iscsi class: Add new NETLINK_ISCSI messages for cnic/bnx2i driver Michael Chan
2009-05-23 21:11 ` [PATCH 2/4] bnx2: Add support for CNIC driver Michael Chan
2009-05-23 21:11 ` [PATCH 4/4] bnx2i: Add bnx2i iSCSI driver Michael Chan
2009-05-26 16:37 ` Grant Grundler
2009-05-26 16:49 ` Michael Chan
2009-05-26 17:03 ` Grant Grundler
[not found] ` <1243113110-29635-1-git-send-email-mchan-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2009-05-23 21:11 ` [PATCH 3/4] cnic: Add new Broadcom CNIC driver Michael Chan
2009-05-25 15:19 ` Rolf Eike Beer
2009-05-26 5:35 ` Michael Chan
2009-05-27 2:35 ` Mike Christie [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=4A1CA706.1020108@cs.wisc.edu \
--to=michaelc-hcno3ddehluvc3sceru5cw@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=anilgv-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=benli-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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