| 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
| ||
|
Date: Thu, 4 Feb 2010 17:36:54 -0700 From: "Kevin Pedretti" <ktpedre@...dia.gov> To: "David Miller" <davem@...emloft.net> cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] seastar - SeaStar Ethernet driver On Thu, 2010-02-04 at 16:13 -0700, David Miller wrote: > From: "Kevin Pedretti" <ktpedre@...dia.gov> > Date: Thu, 4 Feb 2010 16:01:04 -0700 > > > Please let me know if these issues are show-stoppers as far as inclusion > > goes. We would like to get this open-source driver into the kernel so > > us and others with Cray XT systems can start to benefit from it, and > > continue to automatically track kernel API changes. > > I may let it in as-is, thanks for the explanations. > > Could you at least consider perhaps that since it isn't > really ethernet, not pretending that it is may be something > to look at? Sure, I'm open to doing this and would appreciate any example drivers you could point me at. We do need to keep the capability though of talking to Cray's existing proprietary "ethernet" over seastar driver, which the existing driver does. If we go this route of being a non-Ethernet device, do you think it would still be possible to support this? Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists