Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: rasmus.villemoes@xxxxxxxxx
Subject: Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
From: David Miller <davem@xxxxxxxxxxxxx>
Date: Wed, 26 Jun 2019 09:03:56 -0700 (PDT)
Cc: willemdebruijn.kernel@xxxxxxxxx, wg@xxxxxxxxxxxxxx, mkl@xxxxxxxxxxxxxx, Rasmus.Villemoes@xxxxxxxxx, linux-can@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <ff8160d4-3357-9b4f-1840-bbe46195da5a@prevas.dk>
References: <20190624083352.29257-1-rasmus.villemoes@prevas.dk> <CA+FuTSeHhz1kntLyeUfAB4ZbtYjO1=Ornwse-yQbPwo5c-_2=g@mail.gmail.com> <ff8160d4-3357-9b4f-1840-bbe46195da5a@prevas.dk>

From: Rasmus Villemoes <rasmus.villemoes@xxxxxxxxx>
Date: Wed, 26 Jun 2019 09:31:39 +0000

> Perhaps I've misunderstood when to use the net-next prefix - is that
> only for things that should be applied directly to the net-next
> tree?

Yes, it is.

References:
- [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
  - From: Rasmus Villemoes
- Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
  - From: Willem de Bruijn
- Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
  - From: Rasmus Villemoes

Prev by Date: Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
Next by Date: Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
Previous by thread: Re: [PATCH net-next] can: dev: call netif_carrier_off() in register_candev()
Next by thread: j1939: discussion: RX path
Index(es):
- Date
- Thread

[Index of Archives] [Automotive Discussions] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [CAN Bus]

Powered by Linux