All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality
Date: Wed, 5 Dec 2007 04:22:58 +0300	[thread overview]
Message-ID: <20071205042258.486f5738@kernel.crashing.org> (raw)
In-Reply-To: <4755B395.6070104@garzik.org>

On Tue, 04 Dec 2007 15:07:49 -0500
Jeff Garzik wrote:

> Vitaly Bordug wrote:
> > With that patch fixed.c now fully emulates MDIO bus, thus no need
> > to duplicate PHY layer functionality. That, in turn, drastically
> > simplifies the code, and drops down line count.
> > 
> > As an additional bonus, now there is no need to register MDIO bus
> > for each PHY, all emulated PHYs placed on the platform fixed MDIO
> > bus. There is also no more need to pre-allocate PHYs via .config
> > option, this is all now handled dynamically.
> > 
> > p.s. Don't even try to understand patch content! Better: apply patch
> > and look into resulting drivers/net/phy/fixed.c.
> > 
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> > Signed-off-by: Vitaly Bordug <vitb@kernel.crashing.org>
> 
> ACK, I presume this will go via the ppc tree?
> 

Yes, I'll add your ack in next respin and will ask Paul to consider it,
if you don't mind.

-- 
Sincerely, Vitaly

WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality
Date: Wed, 5 Dec 2007 04:22:58 +0300	[thread overview]
Message-ID: <20071205042258.486f5738@kernel.crashing.org> (raw)
In-Reply-To: <4755B395.6070104@garzik.org>

On Tue, 04 Dec 2007 15:07:49 -0500
Jeff Garzik wrote:

> Vitaly Bordug wrote:
> > With that patch fixed.c now fully emulates MDIO bus, thus no need
> > to duplicate PHY layer functionality. That, in turn, drastically
> > simplifies the code, and drops down line count.
> > 
> > As an additional bonus, now there is no need to register MDIO bus
> > for each PHY, all emulated PHYs placed on the platform fixed MDIO
> > bus. There is also no more need to pre-allocate PHYs via .config
> > option, this is all now handled dynamically.
> > 
> > p.s. Don't even try to understand patch content! Better: apply patch
> > and look into resulting drivers/net/phy/fixed.c.
> > 
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> > Signed-off-by: Vitaly Bordug <vitb@kernel.crashing.org>
> 
> ACK, I presume this will go via the ppc tree?
> 

Yes, I'll add your ack in next respin and will ask Paul to consider it,
if you don't mind.

-- 
Sincerely, Vitaly

  reply	other threads:[~2007-12-05  1:23 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 14:29 [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Vitaly Bordug
2007-11-26 14:29 ` Vitaly Bordug
2007-11-26 14:29 ` [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property Vitaly Bordug
2007-11-26 14:29   ` Vitaly Bordug
2007-11-26 15:04   ` Joakim Tjernlund
2007-11-26 15:04     ` [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar forfixed-link property Joakim Tjernlund
2007-11-27 11:39     ` [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property Anton Vorontsov
2007-11-27 11:39       ` Anton Vorontsov
2007-11-27 13:17       ` Joakim Tjernlund
2007-11-27 13:17         ` Joakim Tjernlund
2007-11-27 13:59         ` Anton Vorontsov
2007-11-27 13:59           ` Anton Vorontsov
2007-11-27 14:01           ` Joakim Tjernlund
2007-11-27 14:01             ` Joakim Tjernlund
2007-11-26 14:29 ` [PATCH 3/3] [POWERPC] MPC8349E-mITX: Vitesse 7385 PHY is not connected to the MDIO bus Vitaly Bordug
2007-11-26 14:29   ` Vitaly Bordug
2007-12-01 13:48 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Jochen Friedrich
2007-12-01 13:48   ` Jochen Friedrich
2007-12-01 19:07   ` Vitaly Bordug
2007-12-01 19:07     ` Vitaly Bordug
2007-12-01 21:34   ` Anton Vorontsov
2007-12-01 21:34     ` Anton Vorontsov
2007-12-01 22:22     ` Vitaly Bordug
2007-12-01 22:22       ` Vitaly Bordug
2007-12-01 23:27     ` Stephen Rothwell
2007-12-01 23:27       ` Stephen Rothwell
2007-12-02 11:54     ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHYlayer functionality Joakim Tjernlund
2007-12-02 11:54       ` Joakim Tjernlund
2007-12-02 12:13       ` Anton Vorontsov
2007-12-02 12:13         ` Anton Vorontsov
2007-12-01 21:59 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Jeff Garzik
2007-12-01 21:59   ` Jeff Garzik
2007-12-01 22:16   ` Vitaly Bordug
2007-12-01 22:16     ` Vitaly Bordug
2007-12-04 20:07 ` Jeff Garzik
2007-12-04 20:07   ` Jeff Garzik
2007-12-05  1:22   ` Vitaly Bordug [this message]
2007-12-05  1:22     ` Vitaly Bordug
  -- strict thread matches above, loose matches on Subject: below --
2007-12-06 22:51 Vitaly Bordug
2007-12-06 22:51 ` Vitaly Bordug
2008-01-18  6:45 ` Kumar Gala
2008-01-18  6:45   ` Kumar Gala

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=20071205042258.486f5738@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.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 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.