All of lore.kernel.org
 help / color / mirror / Atom feed
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, yangshuaisong@h-partners.com,
	ningwei15@huawei.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] MAINTAINERS: add myself as a maintainer for Hisilicon Network Subsystem
Date: Thu, 06 Aug 2026 02:00:06 +0000	[thread overview]
Message-ID: <178598160676.605015.9744952869209495856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804130554.871716-1-shaojijie@huawei.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 4 Aug 2026 21:05:54 +0800 you wrote:
> I am already listed as a maintainer for the HNS3 and HIBMCGE drivers,
> but not for the broader Hisilicon Network Subsystem entry, whose file
> pattern covers drivers/net/ethernet/hisilicon/ (e.g. the legacy hns
> driver). As a result, patches to those files are not CC'd to me.
> 
> Add myself alongside Jian Shen to help maintain these legacy Hisilicon
> ethernet drivers and ensure patches in this tree are routed to me.
> 
> [...]

Here is the summary with links:
  - [net] MAINTAINERS: add myself as a maintainer for Hisilicon Network Subsystem
    https://git.kernel.org/netdev/net/c/44871eadd07a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-06  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 13:05 [PATCH net] MAINTAINERS: add myself as a maintainer for Hisilicon Network Subsystem Jijie Shao
2026-08-05 12:38 ` Simon Horman
2026-08-06  2: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=178598160676.605015.9744952869209495856.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=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyonglong@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=ningwei15@huawei.com \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.