From: Jakub Kicinski <kuba@kernel.org>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
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: Thu, 6 Mar 2025 13:46:38 -0800 [thread overview]
Message-ID: <20250306134638.3b4f234e@kernel.org> (raw)
In-Reply-To: <6ae56b95-8736-405b-b090-2ecd2e247988@gmail.com>
On Thu, 6 Mar 2025 23:13:33 +0200 Tariq Toukan wrote:
> >> So no less than two working days for any subsystem.
> >> Okay, now this makes more sense.
> >
> > Could you explain to me why this is a problem for you?
>
> Nothing special about "me" here.
>
> I thought it's obvious. As patches are coming asynchronously, it is not
> rare to won't be able to respond within a single working day.
>
> This becomes significantly rarer with two consecutive working days.
On one thread Saeed is claiming that nVidia is a major netdev
contributor, and pillar of the community.
On another thread it's too hard for the main mlx5 maintainer
to open their inbox once a day to look at patches for their
own driver, that they were CCed on.
next prev parent reply other threads:[~2025-03-06 21:46 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 [this message]
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
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=20250306134638.3b4f234e@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).