From: David Miller <davem@davemloft.net>
To: steve.glendinning@smsc.com
Cc: netdev@vger.kernel.org, ian.saturley@smsc.com
Subject: Re: [RFC PATCH 2/2] refactor full duplex flow control resolution
Date: Tue, 16 Dec 2008 02:00:58 -0800 (PST) [thread overview]
Message-ID: <20081216.020058.57036896.davem@davemloft.net> (raw)
In-Reply-To: <1229258301-5073-3-git-send-email-steve.glendinning@smsc.com>
From: Steve Glendinning <steve.glendinning@smsc.com>
Date: Sun, 14 Dec 2008 12:38:21 +0000
> These 4 drivers have identical full duplex flow control resolution
> functions. This patch changes them all to use one common function.
>
> The function in question decides whether a device should enable TX and
> RX flow control in a standard way (IEEE 802.3-2005 table 28B-3), so this
> should also be useful for other drivers.
>
> Signed-off-by: Steve Glendinning <steve.glendinning@smsc.com>
Looks fine, applied.
Thanks Steve.
next prev parent reply other threads:[~2008-12-16 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 12:38 [RFC PATCH 0/2] unify full duplex flow control resolution Steve Glendinning
2008-12-14 12:38 ` [RFC PATCH 1/2] move flow control definitions to mii.h Steve Glendinning
2008-12-14 12:38 ` [RFC PATCH 2/2] refactor full duplex flow control resolution Steve Glendinning
2008-12-16 10:00 ` David Miller [this message]
2008-12-23 17:45 ` Ben Hutchings
2008-12-29 17:12 ` Steve.Glendinning
2008-12-16 10:00 ` [RFC PATCH 1/2] move flow control definitions to mii.h David Miller
2008-12-18 0:17 ` Andrew Morton
2008-12-18 0:27 ` David Miller
2008-12-23 17:47 ` Ben Hutchings
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=20081216.020058.57036896.davem@davemloft.net \
--to=davem@davemloft.net \
--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).