From: Paolo Abeni <pabeni@redhat.com>
To: Jijie Shao <shaojijie@huawei.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
andrew+netdev@lunn.ch, horms@kernel.org
Cc: shenjian15@huawei.com, liuyonglong@huawei.com,
chenhao418@huawei.com, lantao5@huawei.com,
huangdonghua3@h-partners.com, yangshuaisong@h-partners.com,
jonathan.cameron@huawei.com, salil.mehta@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 net 0/3] There are some bugfix for the HNS3 ethernet driver
Date: Thu, 18 Dec 2025 17:01:22 +0100 [thread overview]
Message-ID: <e128ed6f-5dac-47b7-b329-aecb62d9f8d2@redhat.com> (raw)
In-Reply-To: <20251211023737.2327018-1-shaojijie@huawei.com>
On 12/11/25 3:37 AM, Jijie Shao wrote:
> There are some bugfix for the HNS3 ethernet driver
Next time you should include some actual contents in the cover letter,
i.e. very briefly describing the nature of the issue addressed here.
Thanks,
Paolo
next prev parent reply other threads:[~2025-12-18 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 2:37 [PATCH V2 net 0/3] There are some bugfix for the HNS3 ethernet driver Jijie Shao
2025-12-11 2:37 ` [PATCH V2 net 1/3] net: hns3: using the num_tqps in the vf driver to apply for resources Jijie Shao
2025-12-11 2:37 ` [PATCH V2 net 2/3] net: hns3: using the num_tqps to check whether tqp_index is out of range when vf get ring info from mbx Jijie Shao
2025-12-11 2:37 ` [PATCH V2 net 3/3] net: hns3: add VLAN id validation before using Jijie Shao
2025-12-18 16:01 ` Paolo Abeni [this message]
2025-12-18 16:10 ` [PATCH V2 net 0/3] There are some bugfix for the HNS3 ethernet driver patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2024-03-16 11:10 Jijie Shao
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=e128ed6f-5dac-47b7-b329-aecb62d9f8d2@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=huangdonghua3@h-partners.com \
--cc=jonathan.cameron@huawei.com \
--cc=kuba@kernel.org \
--cc=lantao5@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=yangshuaisong@h-partners.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