From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, matt@codeconstruct.com.au,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, harshtya@google.com
Subject: Re: [PATCH net] mctp: serial: Fix starting value for frame check sequence
Date: Mon, 19 Dec 2022 12:50:16 +0000 [thread overview]
Message-ID: <167145421600.10746.10337384652720939675.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221216034409.27174-1-jk@codeconstruct.com.au>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 16 Dec 2022 11:44:09 +0800 you wrote:
> RFC1662 defines the start state for the crc16 FCS to be 0xffff, but
> we're currently starting at zero.
>
> This change uses the correct start state. We're only early in the
> adoption for the serial binding, so there aren't yet any other users to
> interface to.
>
> [...]
Here is the summary with links:
- [net] mctp: serial: Fix starting value for frame check sequence
https://git.kernel.org/netdev/net/c/2856a62762c8
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:[~2022-12-19 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 3:44 [PATCH net] mctp: serial: Fix starting value for frame check sequence Jeremy Kerr
2022-12-16 16:41 ` Alexander H Duyck
2022-12-17 6:44 ` Jeremy Kerr
2022-12-17 20:59 ` Alexander Duyck
2022-12-18 1:32 ` Jeremy Kerr
2022-12-19 12:50 ` 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=167145421600.10746.10337384652720939675.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harshtya@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 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 NNTP newsgroup(s).