From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>, jelsasser@appneta.com
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net] ixgbe: recognize 1000BaseLX SFP modules as 1Gbps
Date: Tue, 27 Nov 2018 08:27:33 -0800 [thread overview]
Message-ID: <2c43f30e8af44350d2585e48f4fade5e8b93ce0a.camel@intel.com> (raw)
In-Reply-To: <20181126.205247.1196368459821644290.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Mon, 2018-11-26 at 20:52 -0800, David Miller wrote:
> From: Josh Elsasser <jelsasser@appneta.com>
> Date: Mon, 26 Nov 2018 16:54:11 -0800
>
> > Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:
> >
> > > No need to re-spin the patch, just reply with the additional
> > > "Fixes"
> > > tag and if patchwork does not pick it up, I will add it to the
> > > patch I
> > > have in my tree for validation and review.
> >
> > Thanks, let’s try that.
> >
> > Fixes: e23f33367882 ("ixgbe: Fix 1G and 10G link stability for
> > X550EM_x SFP+”)
>
> Unfortunately, patchwork isn't smart enough to pick up Fixes: tags
> still.
:-( I will get it added to the patch in my tree then. Thanks Dave for
the info.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-27 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 20:57 [PATCH net] ixgbe: recognize 1000BaseLX SFP modules as 1Gbps Josh Elsasser
2018-11-25 11:07 ` Bjørn Mork
2018-11-26 17:54 ` Josh Elsasser
2018-11-26 23:52 ` Jeff Kirsher
2018-11-27 0:54 ` [Intel-wired-lan] " Josh Elsasser
2018-11-27 4:52 ` David Miller
2018-11-27 16:27 ` Jeff Kirsher [this message]
2018-11-27 18:07 ` Florian Fainelli
2018-11-26 23:35 ` Bowers, AndrewX
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=2c43f30e8af44350d2585e48f4fade5e8b93ce0a.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jelsasser@appneta.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).