From: David Miller <davem@davemloft.net>
To: varun@chelsio.com
Cc: netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, nab@linux-iscsi.org,
gerlitz.or@gmail.com, swise@opengridcomputing.com,
james.bottomley@hansenpartnership.com, indranil@chelsio.com,
hariprasad@chelsio.com
Subject: Re: [net-next v3 0/6] common library for Chelsio drivers.
Date: Mon, 25 Jul 2016 10:31:40 -0700 (PDT) [thread overview]
Message-ID: <20160725.103140.102549831819762477.davem@davemloft.net> (raw)
In-Reply-To: <cover.1469121308.git.varun@chelsio.com>
From: Varun Prakash <varun@chelsio.com>
Date: Thu, 21 Jul 2016 22:57:13 +0530
> Hi,
>
> This patch series adds common library module(libcxgb.ko)
> for Chelsio drivers to remove duplicate code.
>
> This series moves common iSCSI DDP Page Pod manager
> code from cxgb4.ko to libcxgb.ko, earlier this code
> was used by only cxgbit.ko now it is used by
> three Chelsio iSCSI drivers cxgb3i, cxgb4i, cxgbit.
>
> In future this module will have common connection
> management and hardware specific code that can
> be shared by multiple Chelsio drivers(cxgb4,
> csiostor, iw_cxgb4, cxgb4i, cxgbit).
>
> Please review.
>
> Thanks
>
> -v3
> - removed unused module init and exit functions.
Series applied.
prev parent reply other threads:[~2016-07-25 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 17:27 [net-next v3 0/6] common library for Chelsio drivers Varun Prakash
2016-07-21 17:27 ` [net-next v3 1/6] libcxgb: add library module " Varun Prakash
2016-07-21 17:27 ` [net-next v3 2/6] cxgb3i,cxgb4i,libcxgbi: remove iSCSI DDP support Varun Prakash
2016-07-21 17:27 ` [net-next v3 3/6] cxgb4i,libcxgbi: add " Varun Prakash
2016-07-21 17:27 ` [net-next v3 4/6] cxgb3i: " Varun Prakash
2016-07-21 17:27 ` [net-next v3 5/6] libcxgb: export ppm release and tagmask set api Varun Prakash
2016-07-21 17:27 ` [net-next v3 6/6] cxgb3i,cxgb4i: fix symbol not declared sparse warning Varun Prakash
2016-07-25 17:31 ` David Miller [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=20160725.103140.102549831819762477.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=hariprasad@chelsio.com \
--cc=indranil@chelsio.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.com \
--cc=target-devel@vger.kernel.org \
--cc=varun@chelsio.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).