From: Jakub Kicinski <kuba@kernel.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Yixun Lan <dlan@kernel.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
netdev@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] net: spacemit: Remove unused buff_addr fields
Date: Wed, 4 Mar 2026 14:05:35 -0800 [thread overview]
Message-ID: <20260304140535.678e65f2@kernel.org> (raw)
In-Reply-To: <02bbff3d-1f27-4b03-a963-660bbb7facee@lunn.ch>
On Wed, 4 Mar 2026 21:57:57 +0100 Andrew Lunn wrote:
> On Tue, Mar 03, 2026 at 05:24:18PM +0800, Vivian Wang wrote:
> > These were never used. Just remove them.
> >
> > Fixes: bfec6d7f2001 ("net: spacemit: Add K1 Ethernet MAC")
>
> If you are giving a Fixes: tag, please use the net tree, not net-next.
Maybe rephrasing what Andrew said slightly - please read
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
and general documentation about Fixes tags. The tags mean there is
a bug which may be impacting users.
next prev parent reply other threads:[~2026-03-04 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 9:24 [PATCH net-next 0/4] net: spacemit: A few minor/theoretical fixes Vivian Wang
2026-03-03 9:24 ` [PATCH net-next 1/4] net: spacemit: Remove unused buff_addr fields Vivian Wang
2026-03-04 20:57 ` Andrew Lunn
2026-03-04 22:05 ` Jakub Kicinski [this message]
2026-03-05 5:55 ` Vivian Wang
2026-03-03 9:24 ` [PATCH net-next 2/4] net: spacemit: Fix error handling in emac_alloc_rx_desc_buffers() Vivian Wang
2026-03-03 9:24 ` [PATCH net-next 3/4] net: spacemit: Fix error handling in emac_tx_mem_map() Vivian Wang
2026-03-03 9:24 ` [PATCH net-next 4/4] net: spacemit: Free rings of memory after unmapping DMA Vivian Wang
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=20260304140535.678e65f2@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dlan@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--cc=vadim.fedorenko@linux.dev \
--cc=wangruikang@iscas.ac.cn \
/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