From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de, andrew@lunn.ch,
f.fainelli@gmail.com, hkallweit1@gmail.com, fugang.duan@nxp.com,
kernel@pengutronix.de, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
festevam@gmail.com, david@protonic.nl, linux@armlinux.org.uk,
philippe.schenker@toradex.com
Subject: Re: [PATCH net-next v1 1/1] net: selftests: add MTU test
Date: Thu, 22 Jul 2021 08:00:04 +0000 [thread overview]
Message-ID: <162694080493.21125.3490963326532033566.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210722073427.26537-1-o.rempel@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 22 Jul 2021 09:34:27 +0200 you wrote:
> Test if we actually can send/receive packets with MTU size. This kind of
> issue was detected on ASIX HW with bogus EEPROM.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> net/core/selftests.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
Here is the summary with links:
- [net-next,v1,1/1] net: selftests: add MTU test
https://git.kernel.org/netdev/net-next/c/802a76affb09
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:[~2021-07-22 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 7:34 [PATCH net-next v1 1/1] net: selftests: add MTU test Oleksij Rempel
2021-07-22 8:00 ` 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=162694080493.21125.3490963326532033566.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=david@protonic.nl \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=philippe.schenker@toradex.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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).