netdev - Re: [PATCH] Consolidate shared code between enic and fnic drivers.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ada4ou6pstx.fsf@cisco.com>
Date:	Tue, 23 Jun 2009 14:02:02 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Hannes Reinecke <hare@...e.de>
Cc:	Scott Feldman <scofeldm@...co.com>,
	James.Bottomley@...senPartnership.com, davem@...emloft.net,
	michaelc@...wisc.edu, gospo@...hat.com, abjoglek@...co.com,
	jeykholt@...co.com, netdev@...r.kernel.org,
	linux-scsi@...r.kernel.org
Subject: Re: [PATCH] Consolidate shared code between enic and fnic drivers.


 > 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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html