From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
stable@vger.kernel.org
Subject: Re: [PATCH net 1/2] can: gs_usb: gs_can_close(): add missing set of CAN state to CAN_STATE_STOPPED
Date: Tue, 25 Jul 2023 00:20:21 +0000 [thread overview]
Message-ID: <169024442105.15014.10559557791748669718.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230724150141.766047-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Mon, 24 Jul 2023 17:01:40 +0200 you wrote:
> After an initial link up the CAN device is in ERROR-ACTIVE mode. Due
> to a missing CAN_STATE_STOPPED in gs_can_close() it doesn't change to
> STOPPED after a link down:
>
> | ip link set dev can0 up
> | ip link set dev can0 down
> | ip --details link show can0
> | 13: can0: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 10
> | link/can promiscuity 0 allmulti 0 minmtu 0 maxmtu 0
> | can state ERROR-ACTIVE restart-ms 1000
>
> [...]
Here is the summary with links:
- [net,1/2] can: gs_usb: gs_can_close(): add missing set of CAN state to CAN_STATE_STOPPED
https://git.kernel.org/netdev/net/c/f8a2da6ec241
- [net,2/2] can: raw: fix lockdep issue in raw_release()
https://git.kernel.org/netdev/net/c/11c9027c983e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-25 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 15:01 [PATCH net 0/2] pull-request: can 2023-07-24 Marc Kleine-Budde
2023-07-24 15:01 ` [PATCH net 1/2] can: gs_usb: gs_can_close(): add missing set of CAN state to CAN_STATE_STOPPED Marc Kleine-Budde
2023-07-25 0:20 ` patchwork-bot+netdevbpf [this message]
2023-07-24 15:01 ` [PATCH net 2/2] can: raw: fix lockdep issue in raw_release() Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=169024442105.15014.10559557791748669718.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).