public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] mpc83xx: UEC: add support for Broadcom BCM5481 Gigabit PHY
Date: Tue, 08 Jan 2008 13:04:50 -0500	[thread overview]
Message-ID: <4783BB42.5040404@gmail.com> (raw)
In-Reply-To: <20080108105018.4d91dd7f.kim.phillips@freescale.com>

Kim Phillips wrote:
> On Tue, 25 Dec 2007 20:01:26 +0300
> Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
>
>   
>> This patch adds basic support for Broadcom BCM5481 PHY,
>> with the quirk needed for at least MPC8360E-RDK.
>>     
>
> ?  the MPC8360E-RDK doesn't exist in the mainline tree.
>
>   
>> Quirk comes from MPC8360E-RDK BSP source, I think author is
>> Peter Barada <peterb@logicpd.com>, but I'm not sure.
>>     
>
> solicit his signoff then?
>
>   
>> There are no openly available specifications for that PHY.
>>
>> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
>>     
>
> Also, shouldn't networking patches go through Ben Warren?
>   
Sorry Kim, but I didn't take it because it was in 83xx code. These 
multi-jurisdictional patches are pretty common, and there doesn't seem 
to be a well-defined way of handling them. In this case, it's pretty 
clearly network code, but I'd like to at least have your 'acked-by' in 
the paper trail. Does this sound like the right way to do it, or am I 
making things too bureaucratic?

regards,
Ben

  reply	other threads:[~2008-01-08 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25 17:01 [U-Boot-Users] [PATCH] mpc83xx: UEC: add support for Broadcom BCM5481 Gigabit PHY Anton Vorontsov
2008-01-08 16:50 ` Kim Phillips
2008-01-08 18:04   ` Ben Warren [this message]
2008-01-08 23:31     ` Kim Phillips
2008-01-08 18:41   ` Anton Vorontsov
2008-01-08 20:29     ` Kim Phillips
2008-01-08 21:18       ` Peter Barada

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=4783BB42.5040404@gmail.com \
    --to=biggerbadderben@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox