From: Jeff Garzik <jeff@garzik.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] ethtool: Fix switch on port type
Date: Tue, 01 Dec 2009 11:11:00 -0500 [thread overview]
Message-ID: <4B154014.3030101@garzik.org> (raw)
In-Reply-To: <1259683615.2831.16.camel@achroite.uk.solarflarecom.com>
On 12/01/2009 11:06 AM, Ben Hutchings wrote:
> The new port type cases in commit 6e0512c 'ethtool: Add Direct Attach
> to the available connector ports' were somehow inserted into the
> switch on duplex type, not on port type. Move them to the correct
> place.
>
> Signed-off-by: Ben Hutchings<bhutchings@solarflare.com>
> ---
> ethtool.c | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
ouch - one of the downsides of git happily merging away without complaint.
applied
prev parent reply other threads:[~2009-12-01 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 16:06 [PATCH] ethtool: Fix switch on port type Ben Hutchings
2009-12-01 16:11 ` 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=4B154014.3030101@garzik.org \
--to=jeff@garzik.org \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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).