From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: jk@codeconstruct.com.au, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net: mctp-serial: Fix for missing tx escapes
Date: Sun, 01 Sep 2024 17:20:30 +0000 [thread overview]
Message-ID: <172521123053.3369914.3873085993439343698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240829074355.1327255-1-matt@codeconstruct.com.au>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 29 Aug 2024 15:43:44 +0800 you wrote:
> The mctp-serial code to add escape characters was incorrect due to an
> off-by-one error. This series adds a test for the chunking which splits
> by escape characters, and fixes the bug.
>
> v2: Fix kunit param const pointer
>
> Matt Johnston (2):
> net: mctp-serial: Add kunit test for next_chunk_len()
> net: mctp-serial: Fix missing escapes on transmit
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: mctp-serial: Add kunit test for next_chunk_len()
https://git.kernel.org/netdev/net/c/4fa9c5181cfe
- [net,v2,2/2] net: mctp-serial: Fix missing escapes on transmit
https://git.kernel.org/netdev/net/c/f962e8361adf
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:[~2024-09-01 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 7:43 [PATCH net v2 0/2] net: mctp-serial: Fix for missing tx escapes Matt Johnston
2024-08-29 7:43 ` [PATCH net v2 1/2] net: mctp-serial: Add kunit test for next_chunk_len() Matt Johnston
2024-08-29 7:43 ` [PATCH net v2 2/2] net: mctp-serial: Fix missing escapes on transmit Matt Johnston
2024-09-01 17:20 ` 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=172521123053.3369914.3873085993439343698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.