Dear Andy Fleming,
In message <1320072373-367-1-git-send-email-aflem...@freescale.com> you wrote:
> We want to move everything to phylib, and we definitely don't want
> new drivers using the miiphy infrastructure.
>
> Signed-off-by: Andy Fleming
> ---
> common/miiphyutil.c | 10 +
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.
> >
> >
On Monday 31 October 2011 10:46:13 Andy Fleming wrote:
> +What:Users of the legacy miiphy_* code
> +When:undetermined
> +
> +Why: We now have a PHY library, which allows everyone to share PHY
> + drivers. All new drivers should use this infrastructure, and
> + all old driver
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
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?
http://gcc.gnu.org/onlinedocs/gcc/Function-Attri
We want to move everything to phylib, and we definitely don't want
new drivers using the miiphy infrastructure.
Signed-off-by: Andy Fleming
---
common/miiphyutil.c | 10 ++
doc/feature-removal-schedule.txt | 11 +++
2 files changed, 21 insertions(+), 0 deletions(
6 matches
Mail list logo
