From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de, Pavel Pisa <ppisa@pikron.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [PATCH net-next 04/11] docs: ctucanfd: fix swapped colors in legend for TX buffer FSM of CTU CAN FD
Date: Tue, 18 Aug 2026 01:24:31 +0200 [thread overview]
Message-ID: <20260817233420.2068204-5-mkl@pengutronix.de> (raw)
In-Reply-To: <20260817233420.2068204-1-mkl@pengutronix.de>
From: Pavel Pisa <ppisa@pikron.com>
The Inaccessible and Accessible legend colors has been swapped
for many years. As I have helped to clean the CTU CAN FD section
of official documentation for mass produced silicon (multiple
models of microcontrollers) with the company representatives,
I have found the problem and propagate correction bask to
the primary CTU CAN FD sources.
Signed-off-by: Pavel Pisa <ppisa@pikron.com>
Link: https://patch.msgid.link/d775feefa1c16d7ea7f42482483c81491f75ce6c.1785574572.git.pisa@cmp.felk.cvut.cz
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
.../networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg b/Documentation/networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg
index 381323423b4c..c8cf0bc49b69 100644
--- a/Documentation/networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg
+++ b/Documentation/networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg
@@ -93,9 +93,9 @@
<ellipse cx="144.827" cy="159.143" rx="10.8866" ry="4.39308"/>
<ellipse cx="59.4364" cy="142.823" rx="7.36455" ry="4.39308"/>
<ellipse cx="144.827" cy="129.196" rx="10.8866" ry="4.39308"/>
- <ellipse cx="143.077" cy="180.53" rx="10.8866" ry="4.39308"/>
</g>
- <ellipse cx="110.386" cy="180.53" rx="10.8866" ry="4.39308" fill="#ffcb35" stroke="#000" stroke-linecap="square" stroke-width=".499999"/>
+ <ellipse cx="110.386" cy="180.53" rx="10.8866" ry="4.39308" fill="#28a4ff" stroke="#000" stroke-linecap="square" stroke-width=".499999"/>
+ <ellipse cx="143.077" cy="180.53" rx="10.8866" ry="4.39308" fill="#ffcb35" stroke="#000" stroke-linecap="square" stroke-width=".499999"/>
<text x="110.90907" y="179.42688" font-size="3.175px" xml:space="preserve"><tspan x="110.90907" y="179.42688" dy="0.60000002" text-align="center" text-anchor="middle">Accessible</tspan><tspan x="110.90907" y="183.39563"><tspan font-size="3.175px" text-align="center" text-anchor="middle">for S</tspan>W</tspan></text>
<text x="143.5869" y="179.52795" xml:space="preserve"><tspan x="143.5869" y="179.52795" dy="1 0 0 0 0 0" font-family="sans-serif" font-size="2.82222px" text-align="center" text-anchor="middle" style="font-variant-caps:normal;font-variant-east-asian:normal;font-variant-ligatures:normal;font-variant-numeric:normal">Inaccessible</tspan><tspan x="143.5869" y="183.36786" font-size="3.175px"><tspan font-size="3.175px" text-align="center" text-anchor="middle">for S</tspan>W</tspan></text>
<g font-size="3.175px">
--
2.53.0
next prev parent reply other threads:[~2026-08-17 23:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 23:24 [PATCH net-next 0/11] pull-request: can-next 2026-08-18 Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 01/11] can: tcan4x5x: put tcan into sleep when removing driver Marc Kleine-Budde
2026-08-18 18:37 ` patchwork-bot+netdevbpf
2026-08-18 18:41 ` patchwork-bot+netdevbpf
2026-08-17 23:24 ` [PATCH net-next 02/11] dt-bindings: can: rockchip: add rk3588 CAN-FD compatible Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 03/11] can: rockchip: add RK3588 CAN support Marc Kleine-Budde
2026-08-17 23:24 ` Marc Kleine-Budde [this message]
2026-08-17 23:24 ` [PATCH net-next 05/11] can: vxcan: support per-netns device unregistration Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 06/11] MAINTAINERS: Replace maintainer for Xilinx CAN driver Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 07/11] dt-bindings: net: can: Convert TI HECC to DT schema Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 08/11] dt-bindings: can: xilinx_can: Document phys property Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 09/11] can: m_can: Use of_property_present() for wakeup-source Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 10/11] drivers: gs_usb: gs_usb_probe(): fix typo in error message Marc Kleine-Budde
2026-08-17 23:24 ` [PATCH net-next 11/11] can: m_can: pci: Remove driver_data 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=20260817233420.2068204-5-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ppisa@pikron.com \
/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