netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
	Francois Romieu <romieu@fr.zoreil.com>,
	Hayes Wang <hayeswang@realtek.com>,
	Eric Dumazet <edumazet@google.com>,
	Tom Herbert <therbert@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	Marco Berizzi <pupilla@hotmail.com>,
	linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: 1e918876 breaks r8169 (linux-3.18+)
Date: Sun, 22 Feb 2015 01:41:51 +0100	[thread overview]
Message-ID: <20150222004151.GA4947@louise.pinerecords.com> (raw)
In-Reply-To: <1424548447.5565.48.camel@edumazet-glaptop2.roam.corp.google.com>

> > Sure, just did.  Unfortunately, 3.19.0 + 0bec3b70 + this patch results
> > in a driver that retains the problem.
> 
> OK, could you test following patch instead ?

Yup, but tough luck: 3.19.0 + 0bec3b70 + this patch -> problem present.

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2015-02-22  0:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150203100816.GA5807@louise.pinerecords.com>
     [not found] ` <20150203104214.GG24751@breakpoint.cc>
     [not found]   ` <20150210154536.GB16264@breakpoint.cc>
     [not found]     ` <20150221101512.GB17223@louise.pinerecords.com>
     [not found]       ` <20150221103104.GA26574@breakpoint.cc>
2015-02-21 16:22         ` 1e918876 breaks r8169 (linux-3.18+) Eric Dumazet
2015-02-21 17:46           ` Florian Westphal
2015-02-21 18:09             ` Eric Dumazet
2015-02-21 18:32               ` Florian Westphal
2015-02-21 19:26             ` Tomas Szepe
2015-02-21 19:05           ` Tomas Szepe
2015-02-21 19:54             ` Eric Dumazet
2015-02-22  0:41               ` Tomas Szepe [this message]
2015-02-22 20:57                 ` David Miller

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=20150222004151.GA4947@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=fw@strlen.de \
    --cc=hayeswang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pupilla@hotmail.com \
    --cc=romieu@fr.zoreil.com \
    --cc=therbert@google.com \
    /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).