From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH-RFC] drivers: net: ethernet: intel: e1000e: fix ethtool autoneg off for fiber
Date: Wed, 30 Mar 2016 12:44:09 -0700 [thread overview]
Message-ID: <1459367049.2903.7.camel@intel.com> (raw)
In-Reply-To: <56FC2A62.6040206@cisco.com>
On Wed, 2016-03-30 at 12:34 -0700, Daniel Walker wrote:
>
> So Intel maintainers (Jeff, Jesse, Shannon, Carolyn, Don, Bruce, and
> John)
>
> I'm assuming no comments means this patch is acceptable , and I will?
> resubmit it without the RFC. Is that acceptable ?
I personally do not see an issue with the patch, go ahead and submit it
as a non-RFC and I will make sure that the e1000e maintainer (Dima
Ruinskly) reviews it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160330/f0335fdc/attachment.asc>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Daniel Walker <danielwa@cisco.com>, dima.ruinskiy@intel.com
Cc: Steve Shih <sshih@cisco.com>,
danielwa@fifo99.com, xe-kernel@external.cisco.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [PATCH-RFC] drivers: net: ethernet: intel: e1000e: fix ethtool autoneg off for fiber
Date: Wed, 30 Mar 2016 12:44:09 -0700 [thread overview]
Message-ID: <1459367049.2903.7.camel@intel.com> (raw)
In-Reply-To: <56FC2A62.6040206@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
On Wed, 2016-03-30 at 12:34 -0700, Daniel Walker wrote:
>
> So Intel maintainers (Jeff, Jesse, Shannon, Carolyn, Don, Bruce, and
> John)
>
> I'm assuming no comments means this patch is acceptable , and I will
> resubmit it without the RFC. Is that acceptable ?
I personally do not see an issue with the patch, go ahead and submit it
as a non-RFC and I will make sure that the e1000e maintainer (Dima
Ruinskly) reviews it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-30 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 21:58 [Intel-wired-lan] [PATCH-RFC] drivers: net: ethernet: intel: e1000e: fix ethtool autoneg off for fiber Daniel Walker
2016-03-25 21:58 ` Daniel Walker
2016-03-30 19:34 ` [Intel-wired-lan] " Daniel Walker
2016-03-30 19:34 ` Daniel Walker
2016-03-30 19:44 ` Jeff Kirsher [this message]
2016-03-30 19:44 ` Jeff Kirsher
2016-04-03 14:23 ` [Intel-wired-lan] " Ruinskiy, Dima
2016-04-03 14:23 ` Ruinskiy, Dima
2016-04-04 23:03 ` Daniel Walker
2016-04-04 23:03 ` Daniel Walker
2016-04-05 13:41 ` Ruinskiy, Dima
2016-04-05 13:41 ` Ruinskiy, Dima
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=1459367049.2903.7.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.