[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zzx2ccp65u+AkxHt@localhost.localdomain>
Date: Tue, 19 Nov 2024 12:28:49 +0100
From: Michal Kubiak <michal.kubiak@...el.com>
To: Justin Lai <justinlai0215@...ltek.com>
CC: "kuba@...nel.org" <kuba@...nel.org>, "davem@...emloft.net"
<davem@...emloft.net>, "edumazet@...gle.com" <edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>, "andrew+netdev@...n.ch"
<andrew+netdev@...n.ch>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "horms@...nel.org" <horms@...nel.org>, Ping-Ke Shih
<pkshih@...ltek.com>, Larry Chiu <larry.chiu@...ltek.com>
Subject: Re: [PATCH net v3 4/4] rtase: Add defines for hardware version id
On Tue, Nov 19, 2024 at 07:22:46AM +0000, Justin Lai wrote:
> >
> > On Mon, Nov 18, 2024 at 12:08:28PM +0800, Justin Lai wrote:
> > > Add defines for hardware version id.
> > >
> > > Signed-off-by: Justin Lai <justinlai0215@...ltek.com>
> > > ---
> > > drivers/net/ethernet/realtek/rtase/rtase.h | 5 ++++-
> > > drivers/net/ethernet/realtek/rtase/rtase_main.c | 12 ++++++------
> > > 2 files changed, 10 insertions(+), 7 deletions(-)
> > >
> >
> > The patch is addressed to the "net" tree, but "Fixes" tag is missing.
> > Also, the patch does not look like a bugfix it's rather an improvement of coding
> > style with no functional changes. That's why I doubt it should go to the "net"
> > tree.
> >
> > Thanks,
> > Michal
>
> Hi Michal,
>
> This patch introduces multiple defines for hardware version IDs, rather
> than addressing any issues related to the function logic, which is why it
> does not include a "Fixes:" tag. The reason for isolating this change in a
> separate patch is to maintain a "single patch, single purpose" approach.
> Additionally, these defines will be used in other patches within the same
> patch set, which is why they are included in this patch set as a whole.
>
> Justin
>
Hi Justin,
I understand the purpose of the patch, however the patch is addressed
to the "net" tree. Each patch sent to "net" tree should have "Fixes" tag,
because that tree is for fixes only.
You may consider sending the patch to the "net-next", (which is closed
now because of the merge window).
Thanks,
Michal
Powered by blists - more mailing lists