Re: [PATCH net-next v2 0/4] e1000e: ethtool setfeatures fixes + loopback

[David Decotigny]

Jeff, Bruce,

Please drop this patch series as I was informed that:
 - http://patchwork.ozlabs.org/patch/95175/ already implemented
loopback for ethtool and is under review. Please note, though, that
the version (patch 2) I submitted builds on top of newer net-next
changes
 - Maciej Åenczykowski would prefer not to use the version I sent for
patches 3 and 4, and will provide an improved patch

I will mark the series as rejected on patchwork and will resend patch
1 (fix) as "v3".

My apologies for this hick-up.

Regards,

--
David Decotigny



On Tue, Nov 22, 2011 at 12:46 PM, Jeff Kirsher
<jeffrey.t.kirsher@xxxxxxxxx> wrote:
> On Tue, 2011-11-22 at 11:23 -0800, David Decotigny wrote:
>> This series fixes a bug in ethtool setfeatures and adds loopback
>> support through ethtool setfeatures.
>>
>> I believe these patches could easily be adapted to e1000, but I don't
>> have the hardware to test.
>>
>> Changes since v1:
>> Â - simplification in patch 1/4 (from MichaÅ MirosÅaw)
>>
>> ############################################
>> # Patch Set Summary:
>>
>> David Decotigny (2):
>> Â net-e1000e: fix ethtool set_features taking new features into account
>> Â Â too late
>> Â net-e1000e: ethtool loopback support
>>
>> Maciej Åenczykowski (2):
>> Â net-e1000e: reworked carrier detection logic
>> Â net-e1000e: Report carrier in loopback mode
>>
>> Âdrivers/net/ethernet/intel/e1000e/e1000.h  |  Â2 +
>> Âdrivers/net/ethernet/intel/e1000e/ethtool.c | Â Â6 +-
>> Âdrivers/net/ethernet/intel/e1000e/netdev.c Â| Â 32 +++++++++++-
>> Âdrivers/net/ethernet/intel/e1000e/phy.c   |  69 +++++++++++++++++----------
>> Â4 files changed, 78 insertions(+), 31 deletions(-)
>>
>
> Thanks David for the patch set. ÂI have added the e1000e patches to my
> queue. ÂAs an fyi, I want Bruce Allan to look over these patches and he
> is out this week on vacation.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/