From: Roland Dreier <rdreier@cisco.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Scott Feldman <scofeldm@cisco.com>,
James.Bottomley@HansenPartnership.com, davem@davemloft.net,
michaelc@cs.wisc.edu, gospo@redhat.com, abjoglek@cisco.com,
jeykholt@cisco.com, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Consolidate shared code between enic and fnic drivers.
Date: Tue, 23 Jun 2009 14:02:02 -0700 [thread overview]
Message-ID: <ada4ou6pstx.fsf@cisco.com> (raw)
In-Reply-To: <4A3A090B.9020306@suse.de> (Hannes Reinecke's message of "Thu, 18 Jun 2009 11:29:47 +0200")
> Hmm. Seeing that we're getting more and more of these type of drivers
> (cf bnx2 / bnx2i / cnic, enic / fnic, and at least one other in the pipe)
> one does wonder whether we should establish a separate directory for
> these kind of things.
> drivers/virtual or drivers/shared springs to mind.
>
> Having them in the network directory is probably not the
> correct choice.
Good idea. Maybe I'll post a patch to do that, since one of the drivers
I maintain (mlx4) has a similar structure.
- R.
next prev parent reply other threads:[~2009-06-23 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 5:05 [PATCH] Consolidate shared code between enic and fnic drivers Scott Feldman
2009-06-18 9:29 ` Hannes Reinecke
2009-06-18 17:03 ` Mike Christie
2009-06-18 17:19 ` Scott Feldman
2009-06-18 17:45 ` Mike Christie
2009-06-23 21:03 ` Roland Dreier
2009-06-23 23:53 ` Joe Eykholt
2009-06-25 16:38 ` Roland Dreier
2009-06-23 21:02 ` Roland Dreier [this message]
2009-06-18 14:03 ` Ben Hutchings
2009-06-23 20:58 ` Roland Dreier
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=ada4ou6pstx.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=abjoglek@cisco.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=hare@suse.de \
--cc=jeykholt@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=netdev@vger.kernel.org \
--cc=scofeldm@cisco.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).