From: patchwork-bot+netdevbpf@kernel.org
To: DENG Qingfang <dqfext@gmail.com>
Cc: netdev@vger.kernel.org, nbd@nbd.name, john@phrozen.org,
sean.wang@mediatek.com, Mark-MC.Lee@mediatek.com,
davem@davemloft.net, kuba@kernel.org, matthias.bgg@gmail.com,
linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, andrew@lunn.ch,
frank-w@public-files.de, dwmw2@infradead.org,
opensource@vdorst.com
Subject: Re: [PATCH net-next v2] net: ethernet: mediatek: support setting MTU
Date: Tue, 26 Jan 2021 03:20:10 +0000 [thread overview]
Message-ID: <161163121084.4087.12910254272532951713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210125042046.5599-1-dqfext@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 25 Jan 2021 12:20:46 +0800 you wrote:
> MT762x HW, except for MT7628, supports frame length up to 2048
> (maximum length on GDM), so allow setting MTU up to 2030.
>
> Also set the default frame length to the hardware default 1518.
>
> Signed-off-by: DENG Qingfang <dqfext@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: ethernet: mediatek: support setting MTU
https://git.kernel.org/netdev/net-next/c/4fd59792097a
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-01-26 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 4:20 [PATCH net-next v2] net: ethernet: mediatek: support setting MTU DENG Qingfang
2021-01-25 13:01 ` Andrew Lunn
2021-01-26 2:33 ` Jakub Kicinski
2021-01-26 3: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=161163121084.4087.12910254272532951713.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frank-w@public-files.de \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=sean.wang@mediatek.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).