From: Jakub Kicinski <kuba@kernel.org>
To: Gur Stavi <gur.stavi@huawei.com>
Cc: gongfan <gongfan1@huawei.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>, <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Bjorn Helgaas <helgaas@kernel.org>,
Cai Huoqing <cai.huoqing@linux.dev>,
Xin Guo <guoxin09@huawei.com>,
Shen Chenyang <shenchenyang1@hisilicon.com>,
Zhou Shuai <zhoushuai28@huawei.com>, Wu Like <wulike1@huawei.com>,
Shi Jing <shijing34@huawei.com>,
Meny Yossefi <meny.yossefi@huawei.com>
Subject: Re: [PATCH net-next v03 0/1] net: hinic3: Add a driver for Huawei 3rd gen NIC
Date: Thu, 2 Jan 2025 08:53:51 -0800 [thread overview]
Message-ID: <20250102085351.3436779b@kernel.org> (raw)
In-Reply-To: <cover.1735735608.git.gur.stavi@huawei.com>
On Wed, 1 Jan 2025 15:04:30 +0200 Gur Stavi wrote:
:(
This two docs are required reading:
https://docs.kernel.org/next/maintainer/feature-and-driver-maintainers.html
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
Please read the mailing list. You posted the patches when net-next was closed.
--
pw-bot: defer
pv-bot: closed
next prev parent reply other threads:[~2025-01-02 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 13:04 [PATCH net-next v03 0/1] net: hinic3: Add a driver for Huawei 3rd gen NIC Gur Stavi
2025-01-01 13:04 ` [PATCH net-next v03 1/1] hinic3: module initialization and tx/rx logic Gur Stavi
2025-01-03 8:47 ` [EXTERNAL] " Suman Ghosh
2025-01-07 10:23 ` Gur Stavi
2025-01-07 10:37 ` Gur Stavi
2025-01-07 14:03 ` Gur Stavi
2025-01-08 5:51 ` Gur Stavi
2025-01-02 16:53 ` Jakub Kicinski [this message]
2025-01-05 7:30 ` [PATCH net-next v03 0/1] net: hinic3: Add a driver for Huawei 3rd gen NIC Gur Stavi
2025-01-05 16:32 ` Andrew Lunn
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=20250102085351.3436779b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cai.huoqing@linux.dev \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gongfan1@huawei.com \
--cc=guoxin09@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=helgaas@kernel.org \
--cc=horms@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meny.yossefi@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenchenyang1@hisilicon.com \
--cc=shijing34@huawei.com \
--cc=wulike1@huawei.com \
--cc=zhoushuai28@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).