From: Christoph Hellwig <hch@infradead.org>
To: Anish Bhatt <anish@chelsio.com>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-scsi@vger.kernel.org, davem@davemloft.net,
roland@purestorage.com, hch@infradead.org, michaelc@cs.wisc.edu,
jbottomley@parallels.com, kxie@chelsio.com, leedom@chelsio.com,
hariprasad@chelsio.com, swise@opengridcomputing.com
Subject: Re: [PATCH net-next 0/4] cxgb4i: Add ipv6 support
Date: Wed, 16 Jul 2014 01:08:49 -0700 [thread overview]
Message-ID: <20140716080849.GA29924@infradead.org> (raw)
In-Reply-To: <1405479353-2289-1-git-send-email-anish@chelsio.com>
Hi Anish,
the scsi side changes looks fine to me. Unless you have major updates
to the scsi driver for 3.17 that could cause conflicts I'm fine with
merging the whole series in through the networking tree.
next prev parent reply other threads:[~2014-07-16 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 2:55 [PATCH net-next 0/4] cxgb4i: Add ipv6 support Anish Bhatt
2014-07-16 2:55 ` [PATCH net-next 1/4] cxgb4/iw_cxgb4: Move common defines to cxgb4 Anish Bhatt
[not found] ` <1405479353-2289-1-git-send-email-anish-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2014-07-16 2:55 ` [PATCH net-next 2/4] cxgb4: Export symbols required by cxgb4i for ipv6 support and required defines Anish Bhatt
2014-07-16 2:55 ` [PATCH net-next 3/4] libcxgbi: Add ipv6 api to driver Anish Bhatt
[not found] ` <1405479353-2289-4-git-send-email-anish-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2014-07-17 6:23 ` David Miller
2014-07-16 2:55 ` [PATCH net-next 4/4] cxgb4i: Add ipv6 code to driver, call into libcxgbi ipv6 api Anish Bhatt
2014-07-16 8:08 ` Christoph Hellwig [this message]
[not found] ` <20140716080849.GA29924-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-07-16 8:32 ` [PATCH net-next 0/4] cxgb4i: Add ipv6 support Anish Bhatt
[not found] ` <525DB349B3FB5444AE057A887CB2A8D854356F-m9HP2+76emFEErodcbzraFjMPmZJtkid@public.gmane.org>
2014-07-16 8:47 ` Christoph Hellwig
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=20140716080849.GA29924@infradead.org \
--to=hch@infradead.org \
--cc=anish@chelsio.com \
--cc=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=jbottomley@parallels.com \
--cc=kxie@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=netdev@vger.kernel.org \
--cc=roland@purestorage.com \
--cc=swise@opengridcomputing.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).