netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Tariq Toukan <ttoukan.linux@gmail.com>,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, saeedm@nvidia.com, leon@kernel.org,
	tariqt@nvidia.com, andrew+netdev@lunn.ch,
	Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH net] net/mlx5: Fill out devlink dev info only for PFs
Date: Fri, 7 Mar 2025 08:20:53 -0800	[thread overview]
Message-ID: <20250307082053.6bd879c9@kernel.org> (raw)
In-Reply-To: <ahh3ctzo2gs5zwwhzq33oudr4hmplznewczbfil74zddfabx4n@t7lwrx6eh4ym>

On Fri, 7 Mar 2025 13:35:28 +0100 Jiri Pirko wrote:
> >nvidia's employees patches should go via your tree, in the first place.  
> 
> Why? I've been in Mellanox/Nvidia for almost 10 years and this is
> actually the first time I hit this. I'm used to send patches directly,
> I've been doing that for almost 15+ years and this was never issue.

You probably mostly change the driver together with core, like devlink.
In those cases you can post outside the main stream.

> Where this rule is written down? What changed?

It was always like this, since before I became a maintainer.
I think what happened is Saeed handed the maintainership over
without "writing down" all the rules that we established over
the years.

Obviously he will now probably disagree with me. Because y'all
apparently have no time to review patches, but playing victim
you have all the time in the world for.

There are only two vendors big enough to warrant a special process
(Intel and nVidia), and we make reasonable accommodations (like
the one above) so it's impractical to write all the rules down.

Not to mention the fact that you should perhaps, in an ideal 
world, just try to be a good community member, instead acting
as if we're signing a business contract.

Have a nice weekend.

  reply	other threads:[~2025-03-07 16:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 13:32 [PATCH net] net/mlx5: Fill out devlink dev info only for PFs Jiri Pirko
2025-03-03 16:19 ` Kalesh Anakkur Purayil
2025-03-05 18:55 ` Tariq Toukan
2025-03-06  2:30   ` Jakub Kicinski
2025-03-06 12:47     ` Jiri Pirko
2025-03-06 18:32       ` Jakub Kicinski
2025-03-06 19:20     ` Tariq Toukan
2025-03-06 19:39       ` Jakub Kicinski
2025-03-06 20:12         ` Tariq Toukan
2025-03-06 20:34           ` Jakub Kicinski
2025-03-06 21:13             ` Tariq Toukan
2025-03-06 21:46               ` Jakub Kicinski
2025-03-06 22:26                 ` Saeed Mahameed
2025-03-06 22:32                 ` Gal Pressman
2025-03-06 19:43       ` Jakub Kicinski
2025-03-06 21:16         ` Tariq Toukan
2025-03-07 12:35         ` Jiri Pirko
2025-03-07 16:20           ` Jakub Kicinski [this message]
2025-03-10 12:16             ` Jiri Pirko
2025-03-09  7:50           ` Leon Romanovsky
2025-03-06 19:32     ` Saeed Mahameed
2025-03-06 19:45       ` Jakub Kicinski
2025-03-06 22:11         ` Saeed Mahameed

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=20250307082053.6bd879c9@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=ttoukan.linux@gmail.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).