Re: [PATCH 19/19] e1000: major part of the new API changes

2007-03-30 Thread Kok, Auke
Stephen Hemminger wrote: +s32 +e1000_alloc_zeroed_dev_spec_struct(struct e1000_hw *hw, u32 size) +{ + hw->dev_spec = kmalloc(size, GFP_KERNEL); + + if (!hw->dev_spec) + return -ENOMEM; + + memset(hw->dev_spec, 0, size); + + return E1000_SUCCESS; +} Thi

Re: [PATCH 19/19] e1000: major part of the new API changes

2007-03-30 Thread Stephen Hemminger
+s32 +e1000_alloc_zeroed_dev_spec_struct(struct e1000_hw *hw, u32 size) +{ + hw->dev_spec = kmalloc(size, GFP_KERNEL); + + if (!hw->dev_spec) + return -ENOMEM; + + memset(hw->dev_spec, 0, size); + + return E1000_SUCCESS; +} This is what is wrong with

[PATCH 19/19] e1000: major part of the new API changes

2007-03-29 Thread Auke Kok
From: Jeb Cramer <[EMAIL PROTECTED]> The new hardware initialization code requires us to follow a slightly different approach to setup the device. First the function pointers have to be initialized for the proper hardware type, after which the general initialization calls those in turn to do per-d