| 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: Mon, 12 Mar 2007 10:31:52 -0400 From: Jeff Garzik <jeff@...zik.org> To: Amit Kale <amitkale@...xen.com> CC: Linsys Contractor Mithlesh Thukral <mithlesh@...xen.com>, netdev@...r.kernel.org, netxenproj@...syssoft.com, rob@...xen.com Subject: Re: [PATCH 0/5] NetXen: Driver bug fixes Amit Kale wrote: > On Saturday 10 March 2007 16:52, Jeff Garzik wrote: >> Amit Kale wrote: >>> On Friday 09 March 2007 22:26, Jeff Garzik wrote: >>>> Linsys Contractor Mithlesh Thukral wrote: >>>>> Hi All, >>>>> >>>>> I will be sending updates to NetXen: 1G/10G Ethernet driver in >>>>> subsequent mails. The patches will be with respect to netdev#upstream. >>>> Are you sure you don't want some of these in #upstream-fixes, queued for >>>> 2.6.21-rc? >>> We really want them in both places. If we send them to #upstream-fixes, >>> they'll break #upstream. Should we send them against both of these >>> branches? >> Well, I can drop NetXen patches in #upstream, apply these to >> #upstream-fixes, and wait for a resend? > > Could you do that, please? (drop NetXen patches in #upstream) > > We'll resend them against #upstream-fixes. Will note. Just to be clear, I presume that you will only be resending the bug fixes against #upstream-fixes (2.6.21-rc). The multiple PCI function stuff is way too big and invasive for 2.6.21-rc, which is why I committed that to #upstream (2.6.22). Jeff - 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
Powered by blists - more mailing lists