From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Matt Johnston <matt@codeconstruct.com.au>,
linux-i2c@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] mctp i2c: Enable SMBus ARP discovery
Date: Fri, 23 Jan 2026 11:18:42 +1100 [thread overview]
Message-ID: <9fa316a1a4b16e9f4e1601beeebc5a5e42232dca.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260122080526.4fe83a3a@kernel.org>
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
next prev parent reply other threads:[~2026-01-23 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 9:23 [PATCH v2 0/4] i2c: SMBus ARP support Heikki Krogerus
2026-01-21 9:23 ` [PATCH v2 1/4] i2c: SMBus Address Resolution Protocol implementation for host side Heikki Krogerus
2026-01-21 9:23 ` [PATCH v2 2/4] i2c: Sysfs attribute files for the Unique Device Identifier fields Heikki Krogerus
2026-01-21 9:23 ` [PATCH v2 3/4] mctp i2c: Enable SMBus ARP discovery Heikki Krogerus
2026-01-22 14:36 ` Paolo Abeni
2026-01-22 16:05 ` Jakub Kicinski
2026-01-23 0:18 ` Jeremy Kerr [this message]
2026-01-23 8:46 ` Heikki Krogerus
2026-01-23 18:12 ` Jakub Kicinski
2026-01-21 9:23 ` [PATCH v2 4/4] i2c: Add SMBus ARP target mode test driver Heikki Krogerus
2026-01-24 5:32 ` [PATCH v2 0/4] i2c: SMBus ARP support Jeremy Kerr
2026-01-26 13:56 ` Heikki Krogerus
2026-01-27 0:32 ` Jeremy Kerr
2026-01-27 13:52 ` Heikki Krogerus
2026-01-28 10:28 ` Jeremy Kerr
2026-01-28 15:02 ` Heikki Krogerus
2026-01-29 13:43 ` Jeremy Kerr
2026-02-02 13:29 ` Heikki Krogerus
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=9fa316a1a4b16e9f4e1601beeebc5a5e42232dca.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=heikki.krogerus@linux.intel.com \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wsa+renesas@sang-engineering.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