[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9fa316a1a4b16e9f4e1601beeebc5a5e42232dca.camel@codeconstruct.com.au>
Date: Fri, 23 Jan 2026 11:18:42 +1100
From: Jeremy Kerr <jk@...econstruct.com.au>
To: Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Wolfram Sang
<wsa+renesas@...g-engineering.com>, Matt Johnston
<matt@...econstruct.com.au>, linux-i2c@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/4] mctp i2c: Enable SMBus ARP discovery
Hi Heikki and Jakub,
> +1 I don't wanna speak for Jeremy and Matt but with their Ack, and
> assuming there's no dependency in net-next I think i2c tree may
> be the easiest path?
Yes, given this is more i2c- than net-related, I would be fine for the
changes to go via the i2c tree there. Staging the core via i2c and then
(subsequently) this one via net would also work, but seems to be
overkill for a minor change to the net driver.
I have some overall comments on the i2c side though, I'll follow up with
those separately.
Cheers,
Jeremy
Powered by blists - more mailing lists