From: Greg KH <greg@kroah.com>
To: Gabriel C <nix.or.die@gmail.com>
Cc: "rwarsow@gmx.de" <rwarsow@gmx.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Regression in e1000e since Kernel 4.14.3
Date: Tue, 5 Dec 2017 09:53:30 +0100 [thread overview]
Message-ID: <20171205085330.GC16055@kroah.com> (raw)
In-Reply-To: <491f96ed-9394-dd2f-9af8-435159eed347@gmail.com>
On Tue, Dec 05, 2017 at 09:20:33AM +0100, Gabriel C wrote:
> On 05.12.2017 07:19, Greg KH wrote:
> > On Tue, Dec 05, 2017 at 07:18:34AM +0100, Greg KH wrote:
> > > On Tue, Dec 05, 2017 at 12:47:10AM +0100, Gabriel C wrote:
> > > > On 04.12.2017 23:10, rwarsow@gmx.de wrote:
> > > >
> > > > > Hallo
> > > > >
> > > > > someone and I got an regression with e1000e since kernel 4.14.3 and it seems there is 4.14.4 on the way without a fix.
> > > > >
> > > > >
> > > > > bug report is here:
> > > > >
> > > > > https://bugzilla.kernel.org/show_bug.cgi?id=198047
> > > >
> > > > ( added stable and netdev to CC )
> > > >
> > > > Yes I have a box with e1000e and it seems something at least breaks NM after 4.14.3.
> > >
> > > Again, can people try 4.14.5-rc1? It should be resolved there.
> >
> > Oops, that would be 4.14.4-rc1. Any why do you say above that is on the
> > way without a fix, did you test it?
>
> I didn't tested 4.14.4-rc1 but somone from the bug report tested it and told is not resolved.
>
> I'll fire up an build in a bit and let you know.
Great, and maybe cc: the developers and mailing list for this driver at
the same time? :)
next prev parent reply other threads:[~2017-12-05 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 22:10 Regression in e1000e since Kernel 4.14.3 rwarsow
2017-12-04 23:47 ` Gabriel C
2017-12-05 6:18 ` Greg KH
2017-12-05 6:19 ` Greg KH
2017-12-05 8:20 ` Gabriel C
2017-12-05 8:53 ` Greg KH [this message]
2017-12-05 9:16 ` Gabriel C
2017-12-05 9:23 ` Greg KH
2017-12-05 9:55 ` Gabriel C
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=20171205085330.GC16055@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--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).