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,
matthias.schiffer@ew.tq-group.com, msp@baylibre.com
Subject: Re: [PATCH net 1/2] can: m_can: set init flag earlier in probe
Date: Thu, 19 Dec 2024 02:00:32 +0000 [thread overview]
Message-ID: <173457363203.1790990.3275795076100390604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241218121722.2311963-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Wed, 18 Dec 2024 13:10:27 +0100 you wrote:
> From: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
>
> While an m_can controller usually already has the init flag from a
> hardware reset, no such reset happens on the integrated m_can_pci of the
> Intel Elkhart Lake. If the CAN controller is found in an active state,
> m_can_dev_setup() would fail because m_can_niso_supported() calls
> m_can_cccr_update_bits(), which refuses to modify any other configuration
> bits when CCCR_INIT is not set.
>
> [...]
Here is the summary with links:
- [net,1/2] can: m_can: set init flag earlier in probe
https://git.kernel.org/netdev/net/c/fca2977629f4
- [net,2/2] can: m_can: fix missed interrupts with m_can_pci
https://git.kernel.org/netdev/net/c/743375f8deee
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:[~2024-12-19 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 12:10 [PATCH net 0/2] pull-request: can 2024-12-18 Marc Kleine-Budde
2024-12-18 12:10 ` [PATCH net 1/2] can: m_can: set init flag earlier in probe Marc Kleine-Budde
2024-12-19 2:00 ` patchwork-bot+netdevbpf [this message]
2024-12-18 12:10 ` [PATCH net 2/2] can: m_can: fix missed interrupts with m_can_pci Marc Kleine-Budde
2024-12-19 1:51 ` Jakub Kicinski
2024-12-19 1:54 ` [PATCH net 0/2] pull-request: can 2024-12-18 Jakub Kicinski
2024-12-19 8:03 ` 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=173457363203.1790990.3275795076100390604.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=matthias.schiffer@ew.tq-group.com \
--cc=mkl@pengutronix.de \
--cc=msp@baylibre.com \
--cc=netdev@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).