From: Benjamin Poirier <bpoirier@suse.com>
To: "rwarsow@gmx.de" <rwarsow@gmx.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH] e1000e: Fix e1000_check_for_copper_link_ich8lan return value.
Date: Wed, 10 Jan 2018 10:34:43 +0900 [thread overview]
Message-ID: <20180110013443.xrmta4kcq7yy2olz@f1.synalogic.ca> (raw)
In-Reply-To: <af44aaff-53e6-fb00-2dd6-d47396e56beb@gmx.de>
On 2018/01/10 01:29, rwarsow@gmx.de wrote:
> hallo
>
> any chance to get this patch into stable and 4.15 ?
>
> https://marc.info/?l=linux-kernel&m=151297726823919&w=2
>
It was part of the last network pull request and should be included in
the next mainline release as
4110e02eb45e e1000e: Fix e1000_check_for_copper_link_ich8lan return value.
It's needed in stable branches that include commit 19110cfbb34d
("e1000e: Separate signaling for link check/link up"):
linux-4.14.y
linux-4.9.y
linux-4.4.y
linux-4.1.y
linux-3.18.y
next prev parent reply other threads:[~2018-01-10 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 0:29 [PATCH] e1000e: Fix e1000_check_for_copper_link_ich8lan return value rwarsow
2018-01-10 1:34 ` Benjamin Poirier [this message]
2018-01-14 8:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 1:50 rwarsow
2017-12-18 16:50 rwarsow
2017-12-08 10:45 [PATCH 4.4 71/96] e1000e: Separate signaling for link check/link up Christian Hesse
2017-12-11 7:26 ` [PATCH] e1000e: Fix e1000_check_for_copper_link_ich8lan return value Benjamin Poirier
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=20180110013443.xrmta4kcq7yy2olz@f1.synalogic.ca \
--to=bpoirier@suse.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rwarsow@gmx.de \
--cc=stable@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).