[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170118.172750.1394406967719526972.davem@davemloft.net>
Date: Wed, 18 Jan 2017 17:27:50 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: tklauser@...tanz.ch
Cc: netdev@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
intel-wired-lan@...ts.osuosl.org, devel@...verdev.osuosl.org,
b.a.t.m.a.n@...ts.open-mesh.org, eric.dumazet@...il.com,
j.vosburgh@...il.com, vfalico@...il.com, andy@...yhouse.net,
mlindner@...vell.com, stephen@...workplumber.org
Subject: Re: [PATCH net-next] net: Remove usage of net_device last_rx member
From: Tobias Klauser <tklauser@...tanz.ch>
Date: Wed, 18 Jan 2017 17:45:01 +0100
> The network stack no longer uses the last_rx member of struct net_device
> since the bonding driver switched to use its own private last_rx in
> commit 9f242738376d ("bonding: use last_arp_rx in slave_last_rx()").
>
> However, some drivers still (ab)use the field for their own purposes and
> some driver just update it without actually using it.
>
> Previously, there was an accompanying comment for the last_rx member
> added in commit 4dc89133f49b ("net: add a comment on netdev->last_rx")
> which asked drivers not to update is, unless really needed. However,
> this commend was removed in commit f8ff080dacec ("bonding: remove
> useless updating of slave->dev->last_rx"), so some drivers added later
> on still did update last_rx.
>
> Remove all usage of last_rx and switch three drivers (sky2, atp and
> smc91c92_cs) which actually read and write it to use their own private
> copy in netdev_priv.
>
> Compile-tested with allyesconfig and allmodconfig on x86 and arm.
>
> Cc: Eric Dumazet <eric.dumazet@...il.com>
> Cc: Jay Vosburgh <j.vosburgh@...il.com>
> Cc: Veaceslav Falico <vfalico@...il.com>
> Cc: Andy Gospodarek <andy@...yhouse.net>
> Cc: Mirko Lindner <mlindner@...vell.com>
> Cc: Stephen Hemminger <stephen@...workplumber.org>
> Signed-off-by: Tobias Klauser <tklauser@...tanz.ch>
Applied, thanks.
Powered by blists - more mailing lists