From: David Miller <davem@davemloft.net>
To: afleming@freescale.com
Cc: linux-kernel@vger.kernel.org, kumar.gala@freescale.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] phy: Add support for VSC8234
Date: Fri, 22 Mar 2013 10:13:51 -0400 (EDT) [thread overview]
Message-ID: <20130322.101351.803684806942512280.davem@davemloft.net> (raw)
In-Reply-To: <E1UJ1fR-0004hp-2j@swissweb.swissdisk.com>
From: Andy Fleming <afleming@freescale.com>
Date: Sun, 16 Oct 2011 01:49:49 -0500
> No functional changes other than to recognize this PHYID.
>
> Signed-off-by: Andy Fleming <afleming@freescale.com>
> Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
> Signed-off-by: Ben Collins <ben.c@servergy.com>
Please do not submit patches with the commit date integrated
into your formal email headers.
This screws up archives and patch queue maintainence systems which
order submissions by date.
Thanks.
next prev parent reply other threads:[~2013-03-22 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 6:49 [PATCH] phy: Add support for VSC8234 Andy Fleming
2013-03-22 14:13 ` David Miller [this message]
2013-03-22 14:16 ` Ben Collins
2013-03-22 14:27 ` Fleming Andy-AFLEMING
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=20130322.101351.803684806942512280.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=afleming@freescale.com \
--cc=kumar.gala@freescale.com \
--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