[PATCH 4.14 21/95] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

[PATCH 4.19 025/120] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

[PATCH 5.11 067/306] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

[PATCH 5.10 056/290] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

[PATCH 5.4 034/168] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

[PATCH 4.9 14/78] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

[PATCH 4.4 15/75] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-15 Thread gregkh
nt, and then it checks "netif_xmit_stopped" and finds that the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queu

Re: [PATCH net] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-09 Thread patchwork-bot+netdevbpf
; may still have already > been called. This is because in "__dev_close_many", "ops->ndo_stop" is > called before clearing the "IFF_UP" flag. > > [...] Here is the summary with links: - [net] net: lapbether: Remove netif_start_queue / netif_stop_queue

Re: [PATCH net] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-09 Thread Martin Schiller
at the queue is already stopped. In this case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queue" in "ops->ndo_stop". We also don

[PATCH net] net: lapbether: Remove netif_start_queue / netif_stop_queue

2021-03-07 Thread Xie He
case, it will complain that: "Virtual device ... asks to queue packet!" To prevent "__dev_queue_xmit" from generating this complaint, we should not call "netif_stop_queue" in "ops->ndo_stop". We also don't need to call "netif_start_queue&

Re: netif_start_queue

2001-06-11 Thread Jeff Garzik
sebastien person wrote: > > hi, > > I'm trying to port a ethernet device from 2.2 to 2.4. whith the new way of > dealing with dev->tbusy and dev->start (e.g. by using netif_startqueue for > example) I've understand that the netif_start_queue call put a flag

netif_start_queue

2001-06-11 Thread sebastien person
hi, I'm trying to port a ethernet device from 2.2 to 2.4. whith the new way of dealing with dev->tbusy and dev->start (e.g. by using netif_startqueue for example) I've understand that the netif_start_queue call put a flag that telling the device isn't busy but I can't