Jesse Brandeburg wrote:
On 3/11/06, Jeff Garzik [EMAIL PROTECTED] wrote:
Jeff Kirsher wrote:
Jeff - should a patch be made for 2.6.16 also?
Yes, since this is a small fix and there aren't a ton of e100 changes, I
would prefer that you create a 'git pull' against 2.6.16-rc (latest
Linus git
On 3/11/06, Jeff Garzik [EMAIL PROTECTED] wrote:
Jeff Kirsher wrote:
Jeff - should a patch be made for 2.6.16 also?
Yes, since this is a small fix and there aren't a ton of e100 changes, I
would prefer that you create a 'git pull' against 2.6.16-rc (latest
Linus git tree), and I will pull
Jeff Kirsher wrote:
This patch was diff'd against the latest 'upstream' branch from Garzik's tree.
This patch can be pulled from the following location:
git://198.78.49.142/linux-2.6.git e100-upstream
Jeff - should a patch be made for 2.6.16 also?
Yes, since this is a small fix and there
This patch was diff'd against the latest 'upstream' branch from Garzik's tree.
This patch can be pulled from the following location:
git://198.78.49.142/linux-2.6.git e100-upstream
Jeff - should a patch be made for 2.6.16 also?
Olaf Hering reported a problem on pseries with e100 where ethtool
