From: Jeff Garzik <jeff@garzik.org>
To: Steve Glendinning <steve.glendinning@smsc.com>
Cc: netdev@vger.kernel.org, Ian Saturley <ian.saturley@smsc.com>
Subject: Re: [PATCH 1/2] Rename SMSC phy functions to be more generic
Date: Tue, 29 Apr 2008 01:59:10 -0400 [thread overview]
Message-ID: <4816B92E.7030702@garzik.org> (raw)
In-Reply-To: <1209404206-32551-1-git-send-email-steve.glendinning@smsc.com>
Steve Glendinning wrote:
> Several models of SMSC PHY have the same interrupt status and mask
> registers as the LAN83C185, so these functions can service multiple
> different PHY drivers.
>
> Signed-off-by: Steve Glendinning <steve.glendinning@smsc.com>
> ---
> drivers/net/phy/smsc.c | 14 +++++++-------
> 1 files changed, 7 insertions(+), 7 deletions(-)
applied 1-2
prev parent reply other threads:[~2008-04-29 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 17:36 [PATCH 1/2] Rename SMSC phy functions to be more generic Steve Glendinning
2008-04-29 5:59 ` Jeff Garzik [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=4816B92E.7030702@garzik.org \
--to=jeff@garzik.org \
--cc=ian.saturley@smsc.com \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@smsc.com \
/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;
as well as URLs for NNTP newsgroup(s).