From: patchwork-bot+netdevbpf@kernel.org
To: Jijie Shao <shaojijie@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shenjian15@huawei.com, liuyonglong@huawei.com,
chenhao418@huawei.com, jonathan.cameron@huawei.com,
salil.mehta@huawei.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] There are a cleancode and a parameter check for hns3 driver
Date: Wed, 20 Aug 2025 03:11:50 +0000 [thread overview]
Message-ID: <175565951073.3753798.100437251034921390.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250815100414.949752-1-shaojijie@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 15 Aug 2025 18:04:12 +0800 you wrote:
> This patchset includes:
> 1. a parameter check omitted from fix code in net branch
> https://lore.kernel.org/all/20250723072900.GV2459@horms.kernel.org/
> 2. a small clean code
>
> Jijie Shao (2):
> net: hns3: add parameter check for tx_copybreak and tx_spare_buf_size
> net: hns3: change the function return type from int to bool
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: hns3: add parameter check for tx_copybreak and tx_spare_buf_size
https://git.kernel.org/netdev/net-next/c/e16e973c576f
- [net-next,2/2] net: hns3: change the function return type from int to bool
https://git.kernel.org/netdev/net-next/c/021f989c863b
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:[~2025-08-20 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 10:04 Jijie Shao
2025-08-15 10:04 ` [PATCH net-next 1/2] net: hns3: add parameter check for tx_copybreak and tx_spare_buf_size Jijie Shao
2025-08-15 10:04 ` [PATCH net-next 2/2] net: hns3: change the function return type from int to bool Jijie Shao
2025-08-20 3:11 ` 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=175565951073.3753798.100437251034921390.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@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
all inboxes | Powered by JetHome®