From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jason McMullan <jason.mcmullan@timesys.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
romieu@fr.zoreil.com
Subject: Re: [PATCH] MII bus API for PHY devices
Date: Sat, 13 Nov 2004 12:36:59 +1100 [thread overview]
Message-ID: <1100309819.20593.99.camel@gaston> (raw)
In-Reply-To: <1100278046.17607.23.camel@jmcmullan>
On Fri, 2004-11-12 at 11:47 -0500, Jason McMullan wrote:
> For the 'wake on lan' stuff, could you give me a list of the
> types of features you'd need? I haven't really looked at WOL just yet.
Me neither, though Colin Leroy has, I'll check out his stuff next week.
> We can add WOL, suspend, etc. as needed. I just want to
> get the base infrastructure in first, and gradually start migrating
> phys to the mii_bus on embedded systems.
>
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2004-11-13 1:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 22:48 [PATCH] MII bus API for PHY devices Jason McMullan
2004-11-11 23:54 ` Francois Romieu
2004-11-12 0:07 ` Francois Romieu
2004-11-12 6:15 ` Benjamin Herrenschmidt
2004-11-12 16:47 ` Jason McMullan
2004-11-13 1:36 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 20:18 Manfred Spraul
2004-11-19 21:01 ` Andy Fleming
[not found] <069B6F33-341C-11D9-9652-000393DBC2E8@freescale.com>
2004-11-18 17:52 ` Andy Fleming
2004-11-18 19:34 ` Jason McMullan
2004-11-18 19:50 ` Andy Fleming
2004-11-18 21:00 ` Jason McMullan
2004-11-18 23:26 ` Benjamin Herrenschmidt
2004-11-19 16:41 ` Jason McMullan
2004-11-19 21:18 ` Andy Fleming
2004-11-19 22:43 ` Benjamin Herrenschmidt
2004-11-20 0:04 ` Andy Fleming
2004-11-11 19:45 Jason McMullan
2004-11-11 21:31 ` Francois Romieu
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=1100309819.20593.99.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jason.mcmullan@timesys.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).