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 12:34:48 -0800 [thread overview]
Message-ID: <20250306123448.189615da@kernel.org> (raw)
In-Reply-To: <3faf95ef-022a-412e-879d-c6a326f4267a@gmail.com>
On Thu, 6 Mar 2025 22:12:52 +0200 Tariq Toukan wrote:
> > The exact expectations on the response time will vary by subsystem.
> > The patch review SLA the subsystem had set for itself can sometimes
> > be found in the subsystem documentation. Failing that as a rule of thumb
> > reviewers should try to respond quicker than what is the usual patch
> > review delay of the subsystem maintainer. The resulting expectations
> > may range from two working days for fast-paced subsystems (e.g. networking)
>
> 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?
You're obviously capable of opening your email client once a day.
Are you waiting for QA results or some such?
next prev parent reply other threads:[~2025-03-06 20:34 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 [this message]
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
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=20250306123448.189615da@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 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.