All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leonro@nvidia.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Boris Pismenny <borisp@nvidia.com>, <netdev@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Saeed Mahameed" <saeedm@nvidia.com>
Subject: Re: [PATCH] MAINTAINERS: adjust MELLANOX ETHERNET INNOVA DRIVERS to TLS support removal
Date: Wed, 1 Jun 2022 12:26:18 -0700	[thread overview]
Message-ID: <20220601122618.78b93038@kernel.org> (raw)
In-Reply-To: <YperBiCh1rkKDmSR@unreal>

On Wed, 1 Jun 2022 21:08:06 +0300 Leon Romanovsky wrote:
> On Wed, Jun 01, 2022 at 10:30:39AM -0700, Jakub Kicinski wrote:
> > > Thanks, we will submit it once net-next will be open.  
> > 
> > It should go via net FWIW.  
> 
> I'm slightly confused here.
> 
> According to net policy, the patches that goes there should have Fixes
> line, but Fixes lines are added for bugs [1].
> 
> This forgotten line in MAINTAINERS doesn't cause to any harm to
> users/developers.

Fair, maybe I worded it too strongly. I should have said something like
"FWIW it's okay for MAINTAINERS updates to go via net".

Documentation/ patches and MAINTAINERS are special, they can go into
net without a Fixes tag so that changes to get_maintainer output and
https://www.kernel.org/doc/html/latest/ propagate quickly.

> So when should I put Fixes line in netdev?
> 
> [1] https://lore.kernel.org/netdev/20211208070842.0ace6747@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com/


  reply	other threads:[~2022-06-01 20:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  4:57 [PATCH] MAINTAINERS: adjust MELLANOX ETHERNET INNOVA DRIVERS to TLS support removal Lukas Bulwahn
2022-06-01 10:18 ` Leon Romanovsky
2022-06-01 17:30   ` Jakub Kicinski
2022-06-01 18:08     ` Leon Romanovsky
2022-06-01 19:26       ` Jakub Kicinski [this message]
2022-06-02  6:13         ` Leon Romanovsky
2022-06-10  5:20 ` patchwork-bot+netdevbpf
2022-06-10  5:56   ` 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=20220601122618.78b93038@kernel.org \
    --to=kuba@kernel.org \
    --cc=borisp@nvidia.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.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 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.