From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ben Greear <greearb@candelatech.com>
Cc: David Miller <davem@davemloft.net>,
john.r.fastabend@intel.com, netdev@vger.kernel.org,
e1000-devel@lists.sourceforge.net, therbert@google.com
Subject: Re: [E1000-devel] e1000e tx queue timeout in 3.3.0 (bisected to BQL support for e1000e)
Date: Tue, 01 May 2012 15:42:28 -0700 [thread overview]
Message-ID: <1335912148.2656.11.camel@jtkirshe-mobl> (raw)
In-Reply-To: <4FA05ED2.3030608@candelatech.com>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
On Tue, 2012-05-01 at 15:08 -0700, Ben Greear wrote:
> On 05/01/2012 02:49 PM, David Miller wrote:
> > From: Ben Greear<greearb@candelatech.com>
> > Date: Tue, 01 May 2012 14:10:43 -0700
> >
> >> On 04/20/2012 02:56 PM, Ben Greear wrote:
> >>> On 04/20/2012 02:21 PM, Tom Herbert wrote:
> >>>> Thanks John for pointers to those. Ben, are you running a kernel
> with
> >>>> these patches?
> >>>
> >>> I just tested this on my e1000e and igb machine. With these
> patches,
> >>> I can no longer reproduce the problem.
> >>>
> >>> So, please make sure those are queued up for 3.3 stable!
> >>
> >> Dave: I think these patches below should go to 3.3 stable.
> >>
> >> They are not queued for stable yet as far as I can tell.
> >
> > I let the Intel developers handle -stable submissions for their
> > drivers.
>
> I don't think this is specific to their drivers.
>
> But, as long as _someone_ is pushing it to stable,
> it is fine by me.
>
> Thanks,
> Ben
I will take care of the stable submission's Ben.
Cheers,
Jeff
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-01 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 23:27 e1000e tx queue timeout in 3.3.0 (bisected to BQL support for e1000e) Ben Greear
2012-04-20 2:39 ` Tom Herbert
2012-04-20 6:44 ` Ying Cai
2012-04-20 19:00 ` Ben Greear
2012-04-20 19:05 ` Tom Herbert
2012-04-20 19:13 ` Ben Greear
2012-04-20 19:44 ` John Fastabend
2012-04-20 21:21 ` Tom Herbert
2012-04-20 21:24 ` Ben Greear
2012-04-20 21:56 ` Ben Greear
2012-05-01 21:10 ` [E1000-devel] " Ben Greear
2012-05-01 21:49 ` David Miller
2012-05-01 22:08 ` Ben Greear
2012-05-01 22:42 ` Jeff Kirsher [this message]
2012-05-01 22:46 ` David Miller
2012-05-01 22:52 ` [E1000-devel] " Jeff Kirsher
2012-04-20 6:46 ` Dave, Tushar N
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=1335912148.2656.11.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greearb@candelatech.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--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).