public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?St=C3=A9phane_Graber_=3Cstgraber=40ubuntu=2Ecom=3E?=@ci.codeaurora.org
Cc: kuba@kernel.org, davem@davemloft.net,
	iyappan@os.amperecomputing.com, keyur@os.amperecomputing.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	quan@os.amperecomputing.com, stable@vger.kernel.org,
	toan@os.amperecomputing.com
Subject: Re: [PATCH v2] drivers: net: xgene: Fix regression in CRC stripping
Date: Wed, 23 Mar 2022 17:40:10 +0000	[thread overview]
Message-ID: <164805721038.18073.13961440765175042448.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220322224205.752795-1-stgraber@ubuntu.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 22 Mar 2022 18:42:06 -0400 you wrote:
> From: Stephane Graber <stgraber@ubuntu.com>
> 
> All packets on ingress (except for jumbo) are terminated with a 4-bytes
> CRC checksum. It's the responsability of the driver to strip those 4
> bytes. Unfortunately a change dating back to March 2017 re-shuffled some
> code and made the CRC stripping code effectively dead.
> 
> [...]

Here is the summary with links:
  - [v2] drivers: net: xgene: Fix regression in CRC stripping
    https://git.kernel.org/netdev/net-next/c/e9e6faeafaa0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-03-23 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 14:42 [PATCH] drivers: net: xgene: Fix regression in CRC stripping Stéphane Graber
2022-03-18 21:12 ` Jakub Kicinski
2022-03-22 22:42   ` [PATCH v2] " Stéphane Graber
2022-03-23 17:40     ` 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=164805721038.18073.13961440765175042448.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?St=C3=A9phane_Graber_=3Cstgraber=40ubuntu=2Ecom=3E?=@ci.codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=iyappan@os.amperecomputing.com \
    --cc=keyur@os.amperecomputing.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=quan@os.amperecomputing.com \
    --cc=stable@vger.kernel.org \
    --cc=toan@os.amperecomputing.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