From: Jakub Kicinski <kuba@kernel.org>
To: Cai Huoqing <cai.huoqing@linux.dev>
Cc: shaozhengchao@huawei.com, caihuoqing <caihuoqing@baidu.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Qiao Ma <mqaio@linux.alibaba.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: hinic: Set max_mtu/min_mtu directly to simplify the code.
Date: Thu, 13 Oct 2022 08:35:58 -0700 [thread overview]
Message-ID: <20221013083558.110621be@kernel.org> (raw)
In-Reply-To: <20221013060723.7306-1-cai.huoqing@linux.dev>
On Thu, 13 Oct 2022 14:07:08 +0800 Cai Huoqing wrote:
> From: caihuoqing <caihuoqing@baidu.com>
>
> Set max_mtu/min_mtu directly to avoid making the validity judgment
> when set mtu, because the judgment is made in net/core: dev_validate_mtu,
> so to simplify the code.
>
> Signed-off-by: caihuoqing <caihuoqing@baidu.com>
Alright, if it's just a cleanup then you'll need to wait a few days
(-rc1 will be this Sunday):
# Form letter - net-next is closed
We have already sent the networking pull request for 6.1
and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after 6.1-rc1 is cut.
RFC patches sent for review only are obviously welcome at any time.
prev parent reply other threads:[~2022-10-13 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 6:07 [PATCH v2] net: hinic: Set max_mtu/min_mtu directly to simplify the code Cai Huoqing
2022-10-13 15:35 ` Jakub Kicinski [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=20221013083558.110621be@kernel.org \
--to=kuba@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=caihuoqing@baidu.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mqaio@linux.alibaba.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.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).