linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Konrad Leszczynski <konrad.leszczynski@intel.com>,
	davem@davemloft.net, andrew+netdev@lunn.ch, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	cezary.rojewski@intel.com, sebastian.basierski@intel.com
Subject: Re: [PATCH net-next 0/7] net: stmmac: fixes and new features
Date: Tue, 26 Aug 2025 18:29:53 +0100	[thread overview]
Message-ID: <e4cb25cb-2016-4bab-9cc2-333ea9ae9d3a@linux.dev> (raw)
In-Reply-To: <20250826113247.3481273-1-konrad.leszczynski@intel.com>

On 26/08/2025 12:32, Konrad Leszczynski wrote:
> This series starts with three fixes addressing KASAN panic on ethtool
> usage, Enhanced Descriptor printing and flow stop on TC block setup when
> interface down.
> Everything that follows adds new features such as ARP Offload support,
> VLAN protocol detection and TC flower filter support.

Well, mixing fixes and features in one patchset is not a great idea.
Fixes patches should have Fixes: tags and go to -net tree while features
should go to net-next. It's better to split series into 2 and provide
proper tags for the "fixes" part

  parent reply	other threads:[~2025-08-26 17:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 11:32 [PATCH net-next 0/7] net: stmmac: fixes and new features Konrad Leszczynski
2025-08-26 11:32 ` [PATCH net-next 1/7] net: stmmac: replace memcpy with strscpy in ethtool Konrad Leszczynski
2025-08-27 19:13   ` Simon Horman
2025-08-26 11:32 ` [PATCH net-next 2/7] net: stmmac: correct Tx descriptors debugfs prints Konrad Leszczynski
2025-08-26 11:32 ` [PATCH net-next 3/7] net: stmmac: check if interface is running before TC block setup Konrad Leszczynski
2025-08-26 11:32 ` [PATCH net-next 4/7] net: stmmac: enable ARP Offload on mac_link_up() Konrad Leszczynski
2025-08-26 17:05   ` kernel test robot
2025-08-27 19:28   ` Simon Horman
2025-08-26 11:32 ` [PATCH net-next 5/7] net: stmmac: set TE/RE bits for ARP Offload when interface down Konrad Leszczynski
2025-08-26 11:32 ` [PATCH net-next 6/7] net: stmmac: enhance VLAN protocol detection for GRO Konrad Leszczynski
2025-08-27 19:35   ` Simon Horman
2025-08-26 11:32 ` [PATCH net-next 7/7] net: stmmac: add TC flower filter support for IP EtherType Konrad Leszczynski
2025-08-27 19:37   ` Simon Horman
2025-08-28  9:46     ` Konrad Leszczynski
2025-08-26 17:29 ` Vadim Fedorenko [this message]
2025-08-28  6:47   ` [PATCH net-next 0/7] net: stmmac: fixes and new features Konrad Leszczynski
2025-08-28 12:25     ` Andrew Lunn
2025-08-28 12:51       ` Konrad Leszczynski
2025-08-28 13:21         ` Vadim Fedorenko
2025-08-28 14:40         ` 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=e4cb25cb-2016-4bab-9cc2-333ea9ae9d3a@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=cezary.rojewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=konrad.leszczynski@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sebastian.basierski@intel.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).