From: Ben Collins <benmcollins13@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] phy: Add XGMII phy interface type
Date: Fri, 22 Mar 2013 10:22:05 -0400 [thread overview]
Message-ID: <9CC1FA76-1620-4E0F-82DC-89535633329F@gmail.com> (raw)
In-Reply-To: <20130322.101900.1947638393872492900.davem@davemloft.net>
On Mar 22, 2013, at 10:19 AM, David Miller <davem@davemloft.net> wrote:
> From: Ben Collins <benmcollins13@gmail.com>
> Date: Fri, 22 Mar 2013 10:17:35 -0400
>
>> On Mar 22, 2013, at 10:12 AM, David Miller <davem@davemloft.net> wrote:
>>
>>> From: Ben Collins <ben.c@servergy.com>
>>> Date: Mon, 18 Mar 2013 19:53:42 -0400
>>>
>>>> Used by systems based on certain Freescale SoCs (specifically the
>>>> Servergy CTS-1000 system).
>>>>
>>>> Signed-off-by: Ben Collins <ben.c@servergy.com>
>>>
>>> You can resubmit this patch when you submit a driver upstream that
>>> uses it, so we can see what the use case looks like.
>>
>> That patch is getting sent soon. It's starting out in staging. Should I Cc you on that?
>
> Why don't you wait until the driver is good enough for drivers/net proper?
It's code that I've manually stripped down as a subset of a larger code base for Freescale's DPAA driver. I've only tested it on our (Servergy's) platform, so until it gets more broad testing (and some code review), I want to at least get it into staging so our hardware is supported.
--
Servergy : http://www.servergy.com/
SwissDisk : http://www.swissdisk.com/
Ubuntu : http://www.ubuntu.com/
My Blog : http://ben-collins.blogspot.com/
next prev parent reply other threads:[~2013-03-22 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 23:53 [PATCH] phy: Add XGMII phy interface type Ben Collins
2013-03-22 14:12 ` David Miller
2013-03-22 14:17 ` Ben Collins
2013-03-22 14:19 ` David Miller
2013-03-22 14:22 ` Ben Collins [this message]
2013-03-22 14:27 ` David Miller
2013-03-22 14:33 ` Ben Collins
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=9CC1FA76-1620-4E0F-82DC-89535633329F@gmail.com \
--to=benmcollins13@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox