netdev: ethernet dev_alloc_skb to netdev_alloc_skb

Replaced deprecating dev_alloc_skb with netdev_alloc_skb in drivers/net/ethernet
  - Removed extra skb->dev = dev after netdev_alloc_skb

Signed-off-by: Pradeep A Dalvi <netdev@pradeepdalvi.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 3 insertions, 3 deletions

diff --git a/drivers/net/ethernet/sis/sis900.c b/drivers/net/ethernet/sis/sis900.c
index 91c44688bc3e..f968898c86db 100644
--- a/drivers/net/ethernet/sis/sis900.c
+++ b/drivers/net/ethernet/sis/sis900.c
@@ -1166,7 +1166,7 @@ sis900_init_rx_ring(struct net_device *net_dev)
         for (i = 0; i < NUM_RX_DESC; i++) {
                 struct sk_buff *skb;
 
-                if ((skb = dev_alloc_skb(RX_BUF_SIZE)) == NULL) {
+                if ((skb = netdev_alloc_skb(net_dev, RX_BUF_SIZE)) == NULL) {
                         /* not enough memory for skbuff, this makes a "hole"
                            on the buffer ring, it is not clear how the
                            hardware will react to this kind of degenerated
@@ -1769,7 +1769,7 @@ static int sis900_rx(struct net_device *net_dev)
 
                         /* refill the Rx buffer, what if there is not enough
                          * memory for new socket buffer ?? */
-                        if ((skb = dev_alloc_skb(RX_BUF_SIZE)) == NULL) {
+                        if ((skb = netdev_alloc_skb(net_dev, RX_BUF_SIZE)) == NULL) {
                                 /*
                                  * Not enough memory to refill the buffer
                                  * so we need to recycle the old one so
@@ -1827,7 +1827,7 @@ refill_rx_ring:
                 entry = sis_priv->dirty_rx % NUM_RX_DESC;
 
                 if (sis_priv->rx_skbuff[entry] == NULL) {
-                        if ((skb = dev_alloc_skb(RX_BUF_SIZE)) == NULL) {
+                        if ((skb = netdev_alloc_skb(net_dev, RX_BUF_SIZE)) == NULL) {
                                 /* not enough memory for skbuff, this makes a
                                  * "hole" on the buffer ring, it is not clear
                                  * how the hardware will react to this kind