From: Ido Schimmel <idosch@nvidia.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Petr Machata <petrm@nvidia.com>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
vadimp@nvidia.com
Subject: Re: [PATCH net-next] mlxsw: remove I2C_CLASS_HWMON from drivers w/o detect and address_list
Date: Sun, 28 Jan 2024 16:18:13 +0200 [thread overview]
Message-ID: <ZbZiJU49cDWId4s5@shredder> (raw)
In-Reply-To: <77b5ab8e-20f2-4310-bd89-57db99e2f53b@gmail.com>
On Sat, Jan 27, 2024 at 04:08:18PM +0100, Heiner Kallweit wrote:
> Class-based I2C probing requires detect() and address_list to be
> set in the I2C client driver, see checks in i2c_detect().
> It's misleading to declare I2C_CLASS_HWMON support if this
> precondition isn't met.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> ---
> drivers/net/ethernet/mellanox/mlxsw/minimal.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlxsw/minimal.c b/drivers/net/ethernet/mellanox/mlxsw/minimal.c
> index 6b98c3287..f0ceb196a 100644
> --- a/drivers/net/ethernet/mellanox/mlxsw/minimal.c
> +++ b/drivers/net/ethernet/mellanox/mlxsw/minimal.c
> @@ -708,7 +708,6 @@ static const struct i2c_device_id mlxsw_m_i2c_id[] = {
>
> static struct i2c_driver mlxsw_m_i2c_driver = {
> .driver.name = "mlxsw_minimal",
> - .class = I2C_CLASS_HWMON,
> .id_table = mlxsw_m_i2c_id,
> };
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-01-28 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 15:08 [PATCH net-next] mlxsw: remove I2C_CLASS_HWMON from drivers w/o detect and address_list Heiner Kallweit
2024-01-28 14:18 ` Ido Schimmel [this message]
2024-01-31 2:00 ` patchwork-bot+netdevbpf
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=ZbZiJU49cDWId4s5@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vadimp@nvidia.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).