All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	johannes@sipsolutions.net, corbet@lwn.net,
	skhan@linuxfoundation.org, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] docs: exclude driver and netdevsim bugs
Date: Mon, 15 Jun 2026 09:19:09 -0700	[thread overview]
Message-ID: <20260615091909.78ad2b03@kernel.org> (raw)
In-Reply-To: <20260615091436.GP327369@unreal>

On Mon, 15 Jun 2026 12:14:36 +0300 Leon Romanovsky wrote:
> > +Unless explicitly excluded all bug fixes should be targeting the ``net``
> > +tree and contain an appropriate Fixes tag.
> > +
> > +Obvious exclusions:
> > +
> > + - fixes for bugs which only exist in ``net-next`` should target ``net-next``
> > +   (please still include the Fixes tag in the commit message)
> > + - bugs which cannot be reached, e.g. in code paths not executed given
> > +   current in-tree callers
> > + - fixes for compiler warnings and typos  
> 
> If you decide to resubmit this patch, could you please remove "fixes for
> compiler warnings" from the exclusion list?
> 
> It is quite frustrating to receive a compiler warning originating from a
> different subsystem after the merge window, knowing it will not be
> addressed until the next merge window (around eight weeks later).

Agreed, FWIW, but not planning to resubmit.
I think people misunderstood that I'm __documenting what I already do__
rather than trying to have a discussion :/

      reply	other threads:[~2026-06-15 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 16:29 [PATCH net-next] docs: exclude driver and netdevsim bugs Jakub Kicinski
2026-06-03 19:25 ` Andrew Lunn
2026-06-03 20:13   ` Jakub Kicinski
2026-06-03 20:12 ` Johannes Berg
2026-06-03 22:54   ` Jacob Keller
2026-06-04  6:03 ` kernel test robot
2026-06-15  9:14 ` Leon Romanovsky
2026-06-15 16:19   ` Jakub Kicinski [this message]

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=20260615091909.78ad2b03@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.