mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kenny Hsieh <kenny_hsieh@jabil.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Matt Johnston <matt@codeconstruct.com.au>,
	Andi Shyti <andi.shyti@kernel.org>,
	Peter Rosin <peda@lysator.liu.se>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"davem@davemloft.net" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] mctp i2c: add sysfs control for mux child netdevs
Date: Thu, 15 Oct 2026 08:55:15 +0000	[thread overview]
Message-ID: <DM8PR02MB80878E71AC46BB3358DF3B538E9C2@DM8PR02MB8087.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20853c96b17ea29815ccc34fcc6556032df8291d.camel@codeconstruct.com.au>

Hi Jeremy,

On Tue, 2026-10-13 at 15:02 +0800, Jeremy Kerr wrote:
> More a request than a review: since you're going to the trouble of
> allowing dynamic MCTP devices on mux subordinates, would it be possible
> to also allow this for the root controllers as well?

Yes. v2 drops the root exclusion, so the attribute is attached to every
adapter of the mux tree, the root included. Matt asked for the same
thing, to be able to remove a root netdev at runtime.

  https://lore.kernel.org/netdev/20261015081341.1262695-1-kenny_hsieh@jabil.com/

I have no USB-attached adapter here, so the hotplug ordering is
untested. The attribute is attached from the bus notifier as an adapter
appears, which should cover one arriving after the controller is bound.

BR,
Kenny

      reply	other threads:[~2026-10-15  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  7:31 Kenny Hsieh
2026-10-06  8:01 ` netdev-bot+sashiko
2026-10-07  7:22   ` Kenny Hsieh
2026-10-06 10:31 ` Matt Johnston
2026-10-07  6:06   ` Kenny Hsieh
2026-10-13  7:02 ` Jeremy Kerr
2026-10-15  8:55   ` Kenny Hsieh [this message]

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=DM8PR02MB80878E71AC46BB3358DF3B538E9C2@DM8PR02MB8087.namprd02.prod.outlook.com \
    --to=kenny_hsieh@jabil.com \
    --cc=andi.shyti@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=jk@codeconstruct.com.au \
    --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=peda@lysator.liu.se \
    /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
all inboxes | Powered by JetHome®