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,
reyders1@gmail.com, horms@kernel.org, socketcan@hartkopp.net
Subject: Re: [PATCH net 1/6] Documentation/networking: fix basic node example document ISO 15765-2
Date: Tue, 11 Feb 2025 03:30:32 +0000 [thread overview]
Message-ID: <173924463278.3948401.2091237100978886483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250208115120.237274-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Sat, 8 Feb 2025 12:45:14 +0100 you wrote:
> From: Reyders Morales <reyders1@gmail.com>
>
> In the current struct sockaddr_can tp is member of can_addr. tp is not
> member of struct sockaddr_can.
>
> Signed-off-by: Reyders Morales <reyders1@gmail.com>
> Reviewed-by: Simon Horman <horms@kernel.org>
> Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
> Link: https://patch.msgid.link/20250203224720.42530-1-reyders1@gmail.com
> Fixes: 67711e04254c ("Documentation: networking: document ISO 15765-2")
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
>
> [...]
Here is the summary with links:
- [net,1/6] Documentation/networking: fix basic node example document ISO 15765-2
https://git.kernel.org/netdev/net/c/d0b197b6505f
- [net,2/6] can: j1939: j1939_sk_send_loop(): fix unable to send messages with data length zero
https://git.kernel.org/netdev/net/c/44de577e61ed
- [net,3/6] can: ctucanfd: handle skb allocation failure
https://git.kernel.org/netdev/net/c/9bd24927e3ee
- [net,4/6] can: c_can: fix unbalanced runtime PM disable in error path
https://git.kernel.org/netdev/net/c/257a2cd3eb57
- [net,5/6] can: etas_es58x: fix potential NULL pointer dereference on udev->serial
https://git.kernel.org/netdev/net/c/a1ad2109ce41
- [net,6/6] can: rockchip: rkcanfd_handle_rx_fifo_overflow_int(): bail out if skb cannot be allocated
https://git.kernel.org/netdev/net/c/f7f0adfe64de
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-02-11 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 11:45 [PATCH net 0/6] pull-request: can 2025-02-08 Marc Kleine-Budde
2025-02-08 11:45 ` [PATCH net 1/6] Documentation/networking: fix basic node example document ISO 15765-2 Marc Kleine-Budde
2025-02-11 3:30 ` patchwork-bot+netdevbpf [this message]
2025-02-08 11:45 ` [PATCH net 2/6] can: j1939: j1939_sk_send_loop(): fix unable to send messages with data length zero Marc Kleine-Budde
2025-02-08 11:45 ` [PATCH net 3/6] can: ctucanfd: handle skb allocation failure Marc Kleine-Budde
2025-02-08 11:45 ` [PATCH net 4/6] can: c_can: fix unbalanced runtime PM disable in error path Marc Kleine-Budde
2025-02-08 11:45 ` [PATCH net 5/6] can: etas_es58x: fix potential NULL pointer dereference on udev->serial Marc Kleine-Budde
2025-02-08 11:45 ` [PATCH net 6/6] can: rockchip: rkcanfd_handle_rx_fifo_overflow_int(): bail out if skb cannot be allocated 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=173924463278.3948401.2091237100978886483.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=reyders1@gmail.com \
--cc=socketcan@hartkopp.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.