From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Florian Fainelli" <f.fainelli@gmail.com>,
"Andrew Lunn" <andrew@lunn.ch>
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: mdio_bus: change the bus name to mdio
Date: Fri, 20 Dec 2024 01:34:00 +0000 [thread overview]
Message-ID: <c35f6cd71fcf782e0333b8cc4cabb6d65812f134@linux.dev> (raw)
In-Reply-To: <40cbb576-edd9-40c1-8f7a-8dd6dfa5d7ed@gmail.com>
December 20, 2024 at 12:52 AM, "Florian Fainelli" <f.fainelli@gmail.com> wrote:
>
> On 12/19/24 02:20, Andrew Lunn wrote:
>
> >
> > On Thu, Dec 19, 2024 at 06:04:54PM +0800, Yajun Deng wrote:
> >
> > >
> > > Since all directories under the /sys/bus are bus, we don't need to add a
> > >
> > > bus suffix to mdio.
> > >
> > > This is the only one directory with the bus suffix, sysfs-bus-mdio is
> > >
> > > now a testing ABI, and didn't have Users in it. This is the time to change
> > >
> > > it before it's moved to the stable ABI.
> > >
> >
> > So are you saying nobody has udev scripts referencing MDIO devices?
> >
> > Nobody has scripts accessing the statistics? You don't expect anything
> >
> > in userspace to break because of this change?
> >
> > I personally think it is too late to change this, something will break
> >
> > and somebody will report a regression.
> >
>
> It is too late, merging this patch would be breaking ABI and that is not acceptable.
>
Okay, I got it.
> -- Florian
>
prev parent reply other threads:[~2024-12-20 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 10:04 [PATCH net-next v2] net: mdio_bus: change the bus name to mdio Yajun Deng
2024-12-19 10:20 ` Andrew Lunn
2024-12-19 16:52 ` Florian Fainelli
2024-12-20 1:34 ` Yajun Deng [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=c35f6cd71fcf782e0333b8cc4cabb6d65812f134@linux.dev \
--to=yajun.deng@linux.dev \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.