From: Andrew Lunn <andrew@lunn.ch>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v4 0/2] Add mii_bus to ixgbe driver for dsa devs
Date: Tue, 4 Dec 2018 11:40:38 +0100 [thread overview]
Message-ID: <20181204104038.GB741@lunn.ch> (raw)
In-Reply-To: <c8e3976f-73f9-80be-f6d6-c9a1f064a096@gmail.com>
> Yes the current solution whereby we need to get a hold on the network
> device's struct device reference is not quite ideal, AFAIR, Andrew has
> had the same problem.
Yes, it is not nice, and there is a race with systemd renaming the
interfaces using its naming rules. We need a way to lookup an
interface based on a bus location, or similar, not by name.
Andrew
next prev parent reply other threads:[~2018-12-04 10:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 16:32 [Intel-wired-lan] [PATCH net-next v2 0/2] Add mii_bus to ixgbe driver for dsa devs Steve Douthit
2018-12-03 16:32 ` [Intel-wired-lan] [PATCH net-next v2 1/2] ixgbe: register a mdiobus Steve Douthit
2018-12-03 16:54 ` Andrew Lunn
2018-12-03 17:02 ` Steve Douthit
2018-12-03 17:21 ` Andrew Lunn
2018-12-03 17:59 ` Steve Douthit
2018-12-03 18:18 ` Andrew Lunn
2018-12-03 18:38 ` Steve Douthit
2018-12-03 18:54 ` Andrew Lunn
2018-12-03 16:33 ` [Intel-wired-lan] [PATCH net-next v2 2/2] ixgbe: use mii_bus to handle MII related ioctls Steve Douthit
2018-12-03 18:55 ` [Intel-wired-lan] [PATCH net-next v3 0/2] Add mii_bus to ixgbe driver for dsa devs Steve Douthit
2018-12-03 18:55 ` [Intel-wired-lan] [PATCH net-next v3 1/2] ixgbe: register a mdiobus Steve Douthit
2018-12-03 19:00 ` Andrew Lunn
2018-12-03 19:07 ` Florian Fainelli
2018-12-03 19:44 ` Steve Douthit
2018-12-03 19:45 ` Florian Fainelli
2018-12-03 18:55 ` [Intel-wired-lan] [PATCH net-next v3 2/2] ixgbe: use mii_bus to handle MII related ioctls Steve Douthit
2018-12-03 19:01 ` Andrew Lunn
2018-12-03 19:07 ` Florian Fainelli
2018-12-03 20:14 ` [Intel-wired-lan] [PATCH net-next v4 0/2] Add mii_bus to ixgbe driver for dsa devs Steve Douthit
2018-12-03 20:15 ` [Intel-wired-lan] [PATCH net-next v4 1/2] ixgbe: register a mdiobus Steve Douthit
2018-12-04 16:58 ` Bowers, AndrewX
2018-12-03 20:15 ` [Intel-wired-lan] [PATCH net-next v4 2/2] ixgbe: use mii_bus to handle MII related ioctls Steve Douthit
2018-12-04 16:59 ` Bowers, AndrewX
2018-12-03 20:51 ` [Intel-wired-lan] [PATCH net-next v4 0/2] Add mii_bus to ixgbe driver for dsa devs Florian Fainelli
2018-12-03 23:42 ` Steve Douthit
2018-12-03 23:46 ` Florian Fainelli
2018-12-04 10:40 ` Andrew Lunn [this message]
2018-12-04 16:02 ` Steve Douthit
2018-12-06 15:50 ` [Intel-wired-lan] [PATCH net-next v5 " Steve Douthit
2018-12-06 15:50 ` [Intel-wired-lan] [PATCH net-next v5 1/2] ixgbe: register a mdiobus Steve Douthit
2018-12-06 15:50 ` [Intel-wired-lan] [PATCH net-next v5 2/2] ixgbe: use mii_bus to handle MII related ioctls Steve Douthit
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=20181204104038.GB741@lunn.ch \
--to=andrew@lunn.ch \
--cc=intel-wired-lan@osuosl.org \
/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