All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Benjamin Poirier <bpoirier@suse.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Christian Hesse <list@eworm.de>,
	Amit Pundir <amit.pundir@linaro.org>,
	Sasha Neftin <sasha.neftin@intel.com>,
	Stable <stable@vger.kernel.org>
Subject: Re: [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y
Date: Tue, 19 Dec 2017 15:27:31 -0800	[thread overview]
Message-ID: <1513726051.27260.1.camel@intel.com> (raw)
In-Reply-To: <20171219011012.ilvmd74fqplzhren@f1.synalogic.ca>

[-- Attachment #1: Type: text/plain, Size: 3079 bytes --]

On Tue, 2017-12-19 at 10:10 +0900, Benjamin Poirier wrote:
> On 2017/12/18 12:59, Greg KH wrote:
> > On Mon, Dec 11, 2017 at 10:58:10PM +0100, Christian Hesse wrote:
> > > Greg KH <gregkh@linuxfoundation.org> on Tue, 2017/12/05 08:35:
> > > > On Tue, Dec 05, 2017 at 08:23:27AM +0100, Christian Hesse wrote:
> > > > > Greg KH <gregkh@linuxfoundation.org> on Mon, 2017/12/04 19:37:  
> > > > > > On Mon, Dec 04, 2017 at 04:47:00PM +0100, Christian Hesse
> > > > > > wrote:  
> > > > > > > Amit Pundir <amit.pundir@linaro.org> on Mon, 2017/11/27
> > > > > > > 18:23:    
> > > > > > > > Hi Greg,
> > > > > > > > 
> > > > > > > > Found few e100e upstream fixes from Benjamin Poirier in
> > > > > > > > lede
> > > > > > > > source tree, https://git.lede-project.org/?p=source.git,
> > > > > > > > and
> > > > > > > > these fixes seem reasonable enough for 4.14.y too.
> > > > > > > > 
> > > > > > > > Also submitting an e1000e buffer overrun fix by Sasha
> > > > > > > > Neftin.
> > > > > > > > 
> > > > > > > > Cherry-picked and build tested for linux v4.14.2 for
> > > > > > > > ARCH=arm/arm64.
> > > > > > > > 
> > > > > > > > Regards,
> > > > > > > > Amit Pundir
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Benjamin Poirier (4):
> > > > > > > >   e1000e: Fix error path in link detection
> > > > > > > >   e1000e: Fix return value test
> > > > > > > >   e1000e: Separate signaling for link check/link up
> > > > > > > >   e1000e: Avoid receiver overrun interrupt bursts
> > > > > > > > 
> > > > > > > > Sasha Neftin (1):
> > > > > > > >   e1000e: fix buffer overrun while the I219 is processing
> > > > > > > > DMA
> > > > > > > >     transactions    
> > > > > > > 
> > > > > > > Hello everybody,
> > > > > > > 
> > > > > > > looks like one of these breaks connectivity on my Thinkpad
> > > > > > > X250.
> > > > > > > Just downgraded to linux 4.14.2 to verify.    
> > > > > > 
> > > > > > Can you try the -rc release I just did?  It has a fix for this
> > > > > > series in
> > > > > > it.  
> > > > > 
> > > > > It connects with the notebook's built in ethernet port (did not
> > > > > check with
> > > > > 4.14.3) but still fails to see a link when placed in docking
> > > > > station.  
> > > > 
> > > > Do you have the same issues with 4.15-rc2?
> > > 
> > > Just a short heads-up and final result for this thread...
> > > The issue is fixed with Benjamin's patch:
> > > 
> > > https://patchwork.kernel.org/patch/10104349/
> > 
> > Any word on getting this patch into Linus's tree anytime soon?
> 
> Apparently the intel maintainer was unavailable recently:
> https://www.mail-archive.com/netdev@vger.kernel.org/msg206192.html
> 
> The patch is now in there:
> https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git/l
> og/?h=dev-queue
> but that only makes it slated for 4.16 AFAIK.
> 
> Jeff, given that this issue breaks networking for many people, wouldn't
> it be more appropriate to submit the patch for 4.15?

Yeah, I will send to Dave's net tree (4.15) for inclusion.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-19 23:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 12:53 [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 1/5] e1000e: Fix error path in link detection Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 2/5] e1000e: Fix return value test Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 3/5] e1000e: Separate signaling for link check/link up Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 4/5] e1000e: Avoid receiver overrun interrupt bursts Amit Pundir
2017-11-27 12:53 ` [PATCH for-4.14.y 5/5] e1000e: fix buffer overrun while the I219 is processing DMA transactions Amit Pundir
2017-11-27 12:59 ` [PATCH for-4.14.y 0/5] e1000e: Upstream fixes for linux-4.14.y Greg KH
2017-11-27 13:09   ` [Intel-wired-lan] " Amit Pundir
2017-11-27 13:09     ` Amit Pundir
2017-11-28  9:24     ` [Intel-wired-lan] " Greg KH
2017-11-28  9:24       ` Greg KH
2017-11-27 13:36 ` [Intel-wired-lan] " Amit Pundir
2017-11-27 13:36   ` Amit Pundir
2017-12-04 15:47 ` Christian Hesse
2017-12-04 18:37   ` Greg KH
2017-12-05  7:23     ` Christian Hesse
2017-12-05  7:35       ` Greg KH
2017-12-11 21:58         ` Christian Hesse
2017-12-18 11:59           ` Greg KH
2017-12-19  1:10             ` Benjamin Poirier
2017-12-19 23:27               ` Jeff Kirsher [this message]
2018-01-01  3:53                 ` 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=1513726051.27260.1.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=amit.pundir@linaro.org \
    --cc=bpoirier@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=list@eworm.de \
    --cc=sasha.neftin@intel.com \
    --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 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.