From: Leon Romanovsky <leon@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Jakub Kicinski <kuba@kernel.org>,
Tariq Toukan <ttoukan.linux@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, saeedm@nvidia.com, 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: Sun, 9 Mar 2025 09:50:29 +0200 [thread overview]
Message-ID: <20250309075029.GA10087@unreal> (raw)
In-Reply-To: <ahh3ctzo2gs5zwwhzq33oudr4hmplznewczbfil74zddfabx4n@t7lwrx6eh4ym>
On Fri, Mar 07, 2025 at 01:35:28PM +0100, Jiri Pirko wrote:
> Thu, Mar 06, 2025 at 08:43:55PM +0100, kuba@kernel.org 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.
> Where this rule is written down? What changed?
Maintainer?
I'm second to your feelings.
Long standing contributors sent patches mostly directly. It was definitely
encouraged to send long series through Saeed, but simple, one line fixes were
accepted without extra hop.
It was easy and convenient for everyone.
Thanks
next prev parent reply other threads:[~2025-03-09 7:50 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
2025-03-10 12:16 ` Jiri Pirko
2025-03-09 7:50 ` Leon Romanovsky [this message]
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=20250309075029.GA10087@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@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).