[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zg64b05d.fsf@meer.lwn.net>
Date: Tue, 16 May 2023 12:29:18 -0600
From: Jonathan Corbet <corbet@....net>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Linux Networking <netdev@...r.kernel.org>,
Remote Direct Memory Access Kernel Subsystem
<linux-rdma@...r.kernel.org>,
Linux Documentation <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: Saeed Mahameed <saeedm@...dia.com>,
Leon Romanovsky <leon@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Gal Pressman <gal@...dia.com>,
Rahul Rameshbabu <rrameshbabu@...dia.com>,
Maher Sanalla <msanalla@...dia.com>,
Moshe Shemesh <moshe@...dia.com>,
Tariq Toukan <tariqt@...dia.com>
Subject: Re: [PATCH net v2 0/4] Documentation fixes for Mellanox mlx5
devlink info
Bagas Sanjaya <bagasdotme@...il.com> writes:
> On 5/10/23 10:54, Bagas Sanjaya wrote:
>> Here are fixes for mlx5 devlink info documentation. The first fixes
>> htmldocs warnings on the mainline, while the rest is formatting fixes.
>>
>> Changes since v1 [1]:
>>
>> * Pick up Reviewed-by tags from Leon Romanovsky
>> * Rebase on current net tree
>>
>> [1]: https://lore.kernel.org/linux-doc/20230503094248.28931-1-bagasdotme@gmail.com/
>>
>> Bagas Sanjaya (4):
>> Documentation: net/mlx5: Wrap vnic reporter devlink commands in code
>> blocks
>> Documentation: net/mlx5: Use bullet and definition lists for vnic
>> counters description
>> Documentation: net/mlx5: Add blank line separator before numbered
>> lists
>> Documentation: net/mlx5: Wrap notes in admonition blocks
>>
>> .../ethernet/mellanox/mlx5/devlink.rst | 60 ++++++++++++-------
>> 1 file changed, 37 insertions(+), 23 deletions(-)
>>
>
> Hi jon,
>
> If there is no response from mellanox and/or netdev maintainers,
> would you like to review and pick this series up?
>
They seem OK other than the gratuitous use of Fixes tags. The netdev
maintainers are generally responsive and on top of things, though, and I
don't think there would be any justification for bypassing them here.
Thanks,
jon
Powered by blists - more mailing lists