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,
jacob.kroon@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH net] can: c_can: don't cache TX messages for C_CAN cores
Date: Wed, 28 Sep 2022 18:00:15 +0000 [thread overview]
Message-ID: <166438801585.1002.4512212910588751772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220928090629.1124190-2-mkl@pengutronix.de>
Hello:
This patch was applied to netdev/net.git (master)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Wed, 28 Sep 2022 11:06:29 +0200 you wrote:
> As Jacob noticed, the optimization introduced in 387da6bc7a82 ("can:
> c_can: cache frames to operate as a true FIFO") doesn't properly work
> on C_CAN, but on D_CAN IP cores. The exact reasons are still unknown.
>
> For now disable caching if CAN frames in the TX path for C_CAN cores.
>
> Fixes: 387da6bc7a82 ("can: c_can: cache frames to operate as a true FIFO")
> Link: https://lore.kernel.org/all/20220928083354.1062321-1-mkl@pengutronix.de
> Link: https://lore.kernel.org/all/15a8084b-9617-2da1-6704-d7e39d60643b@gmail.com
> Reported-by: Jacob Kroon <jacob.kroon@gmail.com>
> Tested-by: Jacob Kroon <jacob.kroon@gmail.com>
> Cc: stable@vger.kernel.org # v5.15
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
>
> [...]
Here is the summary with links:
- [net] can: c_can: don't cache TX messages for C_CAN cores
https://git.kernel.org/netdev/net/c/81d192c2ce74
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-28 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220928090629.1124190-1-mkl@pengutronix.de>
2022-09-28 9:06 ` [PATCH net] can: c_can: don't cache TX messages for C_CAN cores Marc Kleine-Budde
2022-09-28 18:00 ` patchwork-bot+netdevbpf [this message]
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=166438801585.1002.4512212910588751772.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jacob.kroon@gmail.com \
--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).