From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] miiphy: Note that miiphy_* API is deprecated
Date: Mon, 31 Oct 2011 14:24:48 -0400 [thread overview]
Message-ID: <201110311424.49748.vapier@gentoo.org> (raw)
In-Reply-To: <10B6933F-AEDD-49DA-9361-5868A5F2F327@freescale.com>
On Monday 31 October 2011 11:12:12 Andy Fleming wrote:
> On Oct 31, 2011, at 10:08 AM, Tabi Timur-B04825 wrote:
> > On Mon, Oct 31, 2011 at 9:46 AM, Andy Fleming wrote:
> >> We want to move everything to phylib, and we definitely don't want
> >> new drivers using the miiphy infrastructure.
> >
> > How about using gcc's deprecated function feature? Or is that too
> > aggressive?
>
> I don't think we want every net driver prior to the last release to create
> a warning. We may switch to that after we get some momentum on switching
> drivers over. The first goal is just to provide information that a new
> driver-writer may see so that the old API doesn't expand.
right, this is why i didn't suggest a #warning or __deprecated before. i'm
pretty sure way more code is using the old phy layer than the new phy layer
atm.
i also want to say that the new phy layer doesn't have all the support that
the old one did ... if you look in include/miiphy.h, there are a few defines at
the end there which are not in linux/mii.h.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111031/296b8b1e/attachment.pgp
next prev parent reply other threads:[~2011-10-31 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 14:46 [U-Boot] [PATCH] miiphy: Note that miiphy_* API is deprecated Andy Fleming
2011-10-31 15:08 ` Tabi Timur-B04825
2011-10-31 15:12 ` Andy Fleming
2011-10-31 18:24 ` Mike Frysinger [this message]
2011-10-31 17:21 ` Mike Frysinger
2011-12-05 21:17 ` Wolfgang Denk
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=201110311424.49748.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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.