Netdev List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Sven Eckelmann <sven@narfation.org>,
	Simon Wunderlich <sw@simonwunderlich.de>,
	netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28
Date: Tue, 4 Aug 2026 15:08:01 +0200	[thread overview]
Message-ID: <37153ad1-5c96-49fc-adee-2a7678414428@redhat.com> (raw)
In-Reply-To: <5248054.31r3eYUQgx@sven-desktop>

On 8/4/26 12:38 PM, Sven Eckelmann wrote:
> On Tuesday, 4 August 2026 12:19:13 CEST Paolo Abeni wrote:
>> On 7/28/26 3:39 PM, Simon Wunderlich wrote:
>>> Dear net maintainers,
>>>
>>> here is a minor bugfix/cleanup pull request of batman-adv to go into net-next.
>>
>> Note that it's preferred to avoid fixes and stable tags for changes
>> targeting the net-next tree. If the fixes are really minor, both could
>> possibly safely dropped. If there is some real problem behind, such
>> changes should instead target the net tree.
>>
>> Can you easily rebase your tree and adjust the PR vs the above?
> 
> I have a different statement from Linus:
> https://lore.kernel.org/lkml/CAHk-=wjt1NiKOdyAMz_DT7NmZ++SizPOhRSi492ukdTnpDzHQw@mail.gmail.com/T/#u
> 
> This is why we started to not send out net.git fixes PRs for things which 
> aren't highly critical or for Linus' "just merged for this release commits"  
> late in the development process.
I actually think netdev preference is consistent with Linus'ask: move
the "fixlet" to net-next.

The additional twist is the ask to drop the stable and fixes tag
(otherwise stable will be flooded, too).

PR are a bit apart from plain series, hence my initial questions WRT how
problematic would be stripping such tags and how impactful are actually
the things addressed in the first 6 patches.

/P


  reply	other threads:[~2026-08-04 13:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 13:39 [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28 Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 01/15] batman-adv: bla: avoid CRC corruption due to parallel claim add Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 02/15] batman-adv: bla: prevent CRC corruptions after claim flush Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 03/15] batman-adv: dat: avoid unaligned fault in IP extraction Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 04/15] batman-adv: dat: atomically update mac addresses Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 05/15] batman-adv: fix TX priority extraction for BATADV_FORW_MCAST Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 06/15] batman-adv: mcast: ensure unshared skb for multicast packets Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 07/15] batman-adv: mcast: linearize skbuff for packet generation Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 08/15] batman-adv: dat: drop non-4addr backwards compatibility Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 09/15] batman-adv: add missing kernel-doc comments Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 10/15] batman-adv: fix kernel-doc for functions holding skb ownership Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 11/15] batman-adv: annotate functions which may reallocate the skbuff Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 12/15] batman-adv: split multiple declarations per line Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 13/15] batman-adv: switch var declarations to reverse x-mas tree order Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 14/15] batman-adv: tt: use atomic flag modifications Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 15/15] batman-adv: tt: simplify NEW flag transition code Simon Wunderlich
2026-08-04  2:19 ` [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28 Jakub Kicinski
2026-08-04  6:55   ` Sven Eckelmann
2026-08-04 13:16     ` Paolo Abeni
2026-08-06 14:49       ` Sven Eckelmann
2026-08-04 10:19 ` Paolo Abeni
2026-08-04 10:38   ` Sven Eckelmann
2026-08-04 13:08     ` Paolo Abeni [this message]
2026-08-04 15:05       ` Sven Eckelmann
2026-08-04 18:32         ` Paolo Abeni
2026-08-04 22:14           ` Jakub Kicinski

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=37153ad1-5c96-49fc-adee-2a7678414428@redhat.com \
    --to=pabeni@redhat.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /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