[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240913135510.1c760f97@kernel.org>
Date: Fri, 13 Sep 2024 13:55:10 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Krzysztof Olędzki <ole@....pl>
Cc: Ido Schimmel <idosch@...dia.com>, Tariq Toukan <tariqt@...dia.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Saeed Mahameed
<saeedm@...dia.com>, Leon Romanovsky <leon@...nel.org>, Yishai Hadas
<yishaih@...dia.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH net-next 1/4] mlx4/mlx5: {mlx4,mlx5e}_en_get_module_info
cleanup
On Wed, 11 Sep 2024 23:38:45 -0700 Krzysztof Olędzki wrote:
> Use SFF8024 constants defined in linux/sfp.h instead of private ones.
>
> Make mlx4_en_get_module_info() and mlx5e_get_module_info() to look
> as close as possible to each other.
>
> Simplify the logic for selecting SFF_8436 vs SFF_8636.
Minor process suggestion, I think you may be sending the patches one by
one. It's best to format them into a new directory and send all at once
with git send-email. Add a cover letter, too.
Powered by blists - more mailing lists