From: Ben Hutchings <bhutchings@solarflare.com>
To: "Choi, David" <David.Choi@Micrel.Com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Doong, Ping" <Ping.Doong@Micrel.Com>
Subject: Re: [patch 3.8-rc2] drivers/net/phy/micrel.c
Date: Wed, 9 Jan 2013 20:54:34 +0000 [thread overview]
Message-ID: <1357764874.2654.4.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <FD9AD8C5375B924CABC56D982DB3A802079D2509@EXMB1.micrel.com>
You'll need to give this a proper subject, like 'micrel_phy: Add support
for new PHYs'.
On Wed, 2013-01-09 at 20:09 +0000, Choi, David wrote:
> From: David J. Choi <david.choi@micrel.com>
>
> Summary of changes:
> This patch is primarily intended to cover more Ethernet phys from Micrel Inc. Additionally it
> .supports ksz8081/91, ksz8061, ksz9051 device.
This is new hardware support which is probably acceptable for the 'net'
tree.
The additional cleanup:
> .changes KSxxx to KSZxxx for unified naming convention. For example, change KS8737 to KSZ8737.
> .changes 9021 to 90x1 for commonly used names between 9021 and 9031 device, as this patch includes
> KSZ9031 which belongs to same family as 9021.
[...]
should be a separate patch that goes into the 'net-next' tree.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2013-01-09 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 20:09 [patch 3.8-rc2] drivers/net/phy/micrel.c Choi, David
2013-01-09 20:54 ` Ben Hutchings [this message]
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=1357764874.2654.4.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=David.Choi@Micrel.Com \
--cc=Ping.Doong@Micrel.Com \
--cc=davem@davemloft.net \
--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