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,
khaledelnaggarlinux@gmail.com
Subject: Re: [PATCH net-next 01/27] can: janz-ican3: use sysfs_emit() in fwinfo_show()
Date: Fri, 25 Jul 2025 23:40:47 +0000 [thread overview]
Message-ID: <175348684700.3447101.5219444722918500838.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250725161327.4165174-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Fri, 25 Jul 2025 18:05:11 +0200 you wrote:
> From: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>
>
> As recommended in Documentation/filesystems/sysfs.rst, show() callbacks
> should use sysfs_emit() or sysfs_emit_at() to format values returned to
> userspace. Replace scnprintf() with sysfs_emit() in fwinfo_show().
>
> Signed-off-by: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>
> Link: https://patch.msgid.link/20250712133609.331904-1-khaledelnaggarlinux@gmail.com
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
>
> [...]
Here is the summary with links:
- [net-next,01/27] can: janz-ican3: use sysfs_emit() in fwinfo_show()
https://git.kernel.org/netdev/net-next/c/21e9b7d11218
- [net-next,02/27] can: ti_hecc: fix -Woverflow compiler warning
https://git.kernel.org/netdev/net-next/c/7cae4d04717b
- [net-next,03/27] can: ti_hecc: Kconfig: add COMPILE_TEST
https://git.kernel.org/netdev/net-next/c/0e7896b95f2b
- [net-next,04/27] can: tscan1: Kconfig: add COMPILE_TEST
https://git.kernel.org/netdev/net-next/c/5323af351e75
- [net-next,05/27] can: tscan1: CAN_TSCAN1 can depend on PC104
https://git.kernel.org/netdev/net-next/c/b7d012e59627
- [net-next,06/27] docs: Fix kernel-doc error in CAN driver
https://git.kernel.org/netdev/net-next/c/2db7a52ca9ed
- [net-next,07/27] can: kvaser_pciefd: Add support to control CAN LEDs on device
https://git.kernel.org/netdev/net-next/c/44f0b630f67e
- [net-next,08/27] can: kvaser_pciefd: Add support for ethtool set_phys_id()
https://git.kernel.org/netdev/net-next/c/e74249a00bf1
- [net-next,09/27] can: kvaser_pciefd: Add intermediate variable for device struct in probe()
https://git.kernel.org/netdev/net-next/c/69a2cb633c27
- [net-next,10/27] can: kvaser_pciefd: Store the different firmware version components in a struct
https://git.kernel.org/netdev/net-next/c/5131f18ffa97
- [net-next,11/27] can: kvaser_pciefd: Store device channel index
https://git.kernel.org/netdev/net-next/c/d54b16b40dda
- [net-next,12/27] can: kvaser_pciefd: Split driver into C-file and header-file.
https://git.kernel.org/netdev/net-next/c/20bc87ae5149
- [net-next,13/27] can: kvaser_pciefd: Add devlink support
https://git.kernel.org/netdev/net-next/c/0d1b337b6d6c
- [net-next,14/27] can: kvaser_pciefd: Expose device firmware version via devlink info_get()
https://git.kernel.org/netdev/net-next/c/3d68ecf4173c
- [net-next,15/27] can: kvaser_pciefd: Add devlink port support
https://git.kernel.org/netdev/net-next/c/6271c8b82730
- [net-next,16/27] Documentation: devlink: add devlink documentation for the kvaser_pciefd driver
https://git.kernel.org/netdev/net-next/c/fed552478e6f
- [net-next,17/27] can: kvaser_usb: Add support to control CAN LEDs on device
https://git.kernel.org/netdev/net-next/c/478248f1bc0c
- [net-next,18/27] can: kvaser_usb: Add support for ethtool set_phys_id()
https://git.kernel.org/netdev/net-next/c/3d7a3de9eba4
- [net-next,19/27] can: kvaser_usb: Assign netdev.dev_port based on device channel index
https://git.kernel.org/netdev/net-next/c/c151b06a087a
- [net-next,20/27] can: kvaser_usb: Add intermediate variables
https://git.kernel.org/netdev/net-next/c/827158a67c86
- [net-next,21/27] can: kvaser_usb: Move comment regarding max_tx_urbs
https://git.kernel.org/netdev/net-next/c/7506789c5335
- [net-next,22/27] can: kvaser_usb: Store the different firmware version components in a struct
https://git.kernel.org/netdev/net-next/c/280eba332b36
- [net-next,23/27] can: kvaser_usb: Store additional device information
https://git.kernel.org/netdev/net-next/c/0020f2ba4099
- [net-next,24/27] can: kvaser_usb: Add devlink support
https://git.kernel.org/netdev/net-next/c/9505a83fc4e1
- [net-next,25/27] can: kvaser_usb: Expose device information via devlink info_get()
https://git.kernel.org/netdev/net-next/c/8720aed90c87
- [net-next,26/27] can: kvaser_usb: Add devlink port support
https://git.kernel.org/netdev/net-next/c/aa6a5c995e16
- [net-next,27/27] Documentation: devlink: add devlink documentation for the kvaser_usb driver
https://git.kernel.org/netdev/net-next/c/6304c4c8476d
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:[~2025-07-25 23:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 16:05 [PATCH net-next 0/27] pull-request: can-next 2025-07-25 Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 01/27] can: janz-ican3: use sysfs_emit() in fwinfo_show() Marc Kleine-Budde
2025-07-25 23:40 ` patchwork-bot+netdevbpf [this message]
2025-07-25 16:05 ` [PATCH net-next 02/27] can: ti_hecc: fix -Woverflow compiler warning Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 03/27] can: ti_hecc: Kconfig: add COMPILE_TEST Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 04/27] can: tscan1: " Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 05/27] can: tscan1: CAN_TSCAN1 can depend on PC104 Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 06/27] docs: Fix kernel-doc error in CAN driver Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 07/27] can: kvaser_pciefd: Add support to control CAN LEDs on device Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 08/27] can: kvaser_pciefd: Add support for ethtool set_phys_id() Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 09/27] can: kvaser_pciefd: Add intermediate variable for device struct in probe() Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 10/27] can: kvaser_pciefd: Store the different firmware version components in a struct Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 11/27] can: kvaser_pciefd: Store device channel index Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 12/27] can: kvaser_pciefd: Split driver into C-file and header-file Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 13/27] can: kvaser_pciefd: Add devlink support Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 14/27] can: kvaser_pciefd: Expose device firmware version via devlink info_get() Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 15/27] can: kvaser_pciefd: Add devlink port support Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 16/27] Documentation: devlink: add devlink documentation for the kvaser_pciefd driver Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 17/27] can: kvaser_usb: Add support to control CAN LEDs on device Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 18/27] can: kvaser_usb: Add support for ethtool set_phys_id() Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 19/27] can: kvaser_usb: Assign netdev.dev_port based on device channel index Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 20/27] can: kvaser_usb: Add intermediate variables Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 21/27] can: kvaser_usb: Move comment regarding max_tx_urbs Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 22/27] can: kvaser_usb: Store the different firmware version components in a struct Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 23/27] can: kvaser_usb: Store additional device information Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 24/27] can: kvaser_usb: Add devlink support Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 25/27] can: kvaser_usb: Expose device information via devlink info_get() Marc Kleine-Budde
2025-07-25 16:05 ` [PATCH net-next 26/27] can: kvaser_usb: Add devlink port support Marc Kleine-Budde
2025-07-28 8:06 ` Jiri Pirko
2025-07-25 16:05 ` [PATCH net-next 27/27] Documentation: devlink: add devlink documentation for the kvaser_usb driver 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=175348684700.3447101.5219444722918500838.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=khaledelnaggarlinux@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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