Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream)

2006-03-03 Thread Jesse Brandeburg
On Fri, 3 Mar 2006, Jeff Garzik wrote: Andrew Morton wrote: Did we fix wake-on-lan? A bit of a generic question :/ There are indeed WOL fixes in there... Other than that, I'll wait for the Intel guys to pop up and answer. AFAIK the answer is unfortunately no. I think the driver may need

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream)

2006-03-03 Thread Jeff Garzik
Andrew Morton wrote: Jeff Garzik <[EMAIL PROTECTED]> wrote: > git://198.78.49.142/linux-2.6.git e1000-upstream Pulled into netdev#upstream, thanks! Did we fix wake-on-lan? A bit of a generic question :/ There are indeed WOL fixes in there... Other than that, I'll wait for the Intel guys

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream)

2006-03-03 Thread Andrew Morton
Jeff Garzik <[EMAIL PROTECTED]> wrote: > > > git://198.78.49.142/linux-2.6.git e1000-upstream > > Pulled into netdev#upstream, thanks! Did we fix wake-on-lan? - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream)

2006-03-03 Thread Jeff Garzik
Jeff Kirsher wrote: On 3/2/06, Jeff Garzik <[EMAIL PROTECTED]> wrote: So, I'll ask you guys to fix up your tree to apply without conflicts to the latest git, and then resubmit the push. You don't have to resend all 19 patches, I've reviewed and approved those already. Jeff Patch 19/

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream)

2006-03-02 Thread Jeff Kirsher
On 3/2/06, Jeff Garzik <[EMAIL PROTECTED]> wrote: > So, I'll ask you guys to fix up your tree to apply without conflicts to > the latest git, and then resubmit the push. You don't have to resend > all 19 patches, I've reviewed and approved those already. > > Jeff Patch 19/19 has to be mod

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream additions for 2.6.17)

2006-03-02 Thread Jeff Garzik
Jeff Kirsher wrote: The following patches were diff'd against Garzik's latest 'master' branch and can be pulled from the following location: git://198.78.49.142/linux-2.6.git e1000-upstream Since (per current thread) I'm pulling everything into #upstream, I apologize for asking you to split i

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream additions for 2.6.17)

2006-03-02 Thread Jeff Kirsher
On 3/2/06, Jeff Garzik <[EMAIL PROTECTED]> wrote: > Your message above indicates they were diff'd against the 'master' > branch, which is not correct. They should be against your fixes branch, > "e1000-patchset", as I described in my previous example. > > Or is this just an email-wording issue, an

Re: [PATCH netdev-2.6 00/19] e1000: driver update (upstream additions for 2.6.17)

2006-03-02 Thread Jeff Garzik
Jeff Kirsher wrote: The following patches were diff'd against Garzik's latest 'master' branch and can be pulled from the following location: git://198.78.49.142/linux-2.6.git e1000-upstream Patches 12-19 are new additions to e1000 for the 2.6.17 kernel. Your message above indicates they were

[PATCH netdev-2.6 00/19] e1000: driver update (upstream additions for 2.6.17)

2006-03-02 Thread Jeff Kirsher
The following patches were diff'd against Garzik's latest 'master' branch and can be pulled from the following location: git://198.78.49.142/linux-2.6.git e1000-upstream Patches 12-19 are new additions to e1000 for the 2.6.17 kernel. 12. Added 82573 controller support to TSO fix 13. Add enabled