From: Thomas Huth <1874676@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1874676] Re: [Feature request] MDIO bus
Date: Wed, 28 Apr 2021 14:57:53 -0000 [thread overview]
Message-ID: <161962187378.11202.10658608638051087969.malone@wampee.canonical.com> (raw)
In-Reply-To: 158772214298.26171.14045550676291595233.malonedeb@soybean.canonical.com
This is an automated cleanup. This bug report has been moved
to QEMU's new bug tracker on gitlab.com and thus gets marked
as 'expired' now. Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/49
** Changed in: qemu
Status: Incomplete => Expired
** Changed in: qemu
Assignee: Philippe Mathieu-Daudé (philmd) => (unassigned)
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #49
https://gitlab.com/qemu-project/qemu/-/issues/49
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1874676
Title:
[Feature request] MDIO bus
Status in QEMU:
Expired
Bug description:
Various network devices open-code a MDIO bus with a dedicated PHY.
Introduce a new MDIO subsystem to
- reuse various duplicated components
- be able to interchange PHYs
- have common tracing
- use libqos to test all the PHYs from different NICs
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1874676/+subscriptions
prev parent reply other threads:[~2021-04-28 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 9:55 [Bug 1874676] [NEW] [Feature request] MDIO bus Philippe Mathieu-Daudé
2020-05-18 8:18 ` [Bug 1874676] " Thomas Huth
2021-04-22 4:15 ` Thomas Huth
2021-04-22 14:37 ` Philippe Mathieu-Daudé
2021-04-28 14:57 ` Thomas Huth [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=161962187378.11202.10658608638051087969.malone@wampee.canonical.com \
--to=1874676@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).