From: patchwork-bot+netdevbpf@kernel.org
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, edumazet@google.com, mkl@pengutronix.de
Subject: Re: [NET 0/2] CAN fixes for 6.5-rc7
Date: Wed, 23 Aug 2023 00:30:24 +0000 [thread overview]
Message-ID: <169275062457.22438.1864998736721387025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230821144547.6658-1-socketcan@hartkopp.net>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Aug 2023 16:45:45 +0200 you wrote:
> Hello Jakub,
>
> as Marc is probably on vacation I send these two fixes directly to the netdev
> mailing list to hopefully get them into the current 6.5 cycle.
>
> The isotp fix removes an unnecessary check which leads to delays and/or a wrong
> error notification.
>
> [...]
Here is the summary with links:
- [NET,1/2] can: isotp: fix support for transmission of SF without flow control
https://git.kernel.org/netdev/net/c/0bfe71159230
- [NET,2/2] can: raw: add missing refcount for memory leak fix
https://git.kernel.org/netdev/net/c/c275a176e4b6
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:[~2023-08-23 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 14:45 [NET 0/2] CAN fixes for 6.5-rc7 Oliver Hartkopp
2023-08-21 14:45 ` [NET 1/2] can: isotp: fix support for transmission of SF without flow control Oliver Hartkopp
2023-08-21 14:45 ` [NET 2/2] can: raw: add missing refcount for memory leak fix Oliver Hartkopp
2023-08-22 7:59 ` Simon Horman
2023-08-22 16:45 ` Oliver Hartkopp
2023-08-22 20:08 ` Simon Horman
2023-08-23 0:30 ` 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=169275062457.22438.1864998736721387025.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).