From: Mike Christie <michaelc@cs.wisc.edu>
To: Karen Xie <kxie@chelsio.com>
Cc: David Miller <davem@davemloft.net>,
linux-scsi@vger.kernel.org, open-iscsi@googlegroups.com,
James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH 0/3 2.6.29] cxgb3i -- driver fixes & updates
Date: Mon, 08 Dec 2008 09:56:30 -0600 [thread overview]
Message-ID: <493D43AE.8090404@cs.wisc.edu> (raw)
In-Reply-To: <8A71B368A89016469F72CD08050AD334D7136A@maui.asicdesigners.com>
Karen Xie wrote:
> Hi, Dave & Mike,
>
> I guess I need some clarification on how this driver code could be merged.
>
I think you want to send a patch with the entire driver like you were
before. Do not send against my branch so James and others do not have to
dig around in there.
> The cxgb3i driver addition consists of 2 parts:
>
> 1. the new cxgb3i driver. It resides under drivers/scsi, this part has the dependency on the open-iscsi core changes I referred in the previous email. I was under the impression this goes into scsi-misc?
>
> 2. some iscsi related changes in cxgb3 driver (driver/net). This part does not have any dependency. Dave, I suppose this part goes into net-next? If so, this does not need Mike's patch at all.
>
There is no dependency with network stuff right (just the cxgb3 driver
which is upstream already)? If so I think it would be easier to just
send the driver through James.
> Thanks a lot.
> Karen
>
> -----Original Message-----
> From: David Miller [mailto:davem@davemloft.net]
> Sent: Sat 12/6/2008 11:53 PM
> To: Karen Xie
> Cc: linux-scsi@vger.kernel.org; open-iscsi@googlegroups.com; michaelc@cs.wisc.edu; James.Bottomley@HansenPartnership.com
> Subject: Re: [PATCH 0/3 2.6.29] cxgb3i -- driver fixes & updates
>
> From: Karen Xie <kxie@chelsio.com>
> Date: Sat, 6 Dec 2008 23:09:36 -0800
>
>> It is based on the cxgb3i branch of Mike's linux-2.6-iscsi tree. It needs the
>> patch Mike sent several days ago on preparing the iscsi core libary for pdu
>> offload (http://marc.info/?l=linux-scsi&m=122819956917473).
>
> If this dependency exists I probably can't pull this into the
> net-next-2.6 then, just FYI but you probably already understand
> this :-)
>
next prev parent reply other threads:[~2008-12-08 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 7:09 [PATCH 0/3 2.6.29] cxgb3i -- driver fixes & updates Karen Xie
2008-12-07 7:53 ` David Miller
2008-12-07 23:05 ` Karen Xie
2008-12-08 15:56 ` Mike Christie [this message]
2008-12-08 17:47 ` Karen Xie
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=493D43AE.8090404@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davem@davemloft.net \
--cc=kxie@chelsio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=open-iscsi@googlegroups.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