From: Eric Dumazet <eric.dumazet@gmail.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Thomas Meyer <thomas@m3y3r.de>,
David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"jcliburn@gmail.com" <jcliburn@gmail.com>,
"chris.snook@gmail.com" <chris.snook@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] atl1c: dont use highprio tx queue
Date: Thu, 16 Feb 2012 14:12:33 +0100 [thread overview]
Message-ID: <1329397953.9395.0.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <CA+5PVA74bejZhPxUAFHaeHLB0NBd7PCRc1sQvmSY7QdmarCWEw@mail.gmail.com>
Le jeudi 16 février 2012 à 07:36 -0500, Josh Boyer a écrit :
> As I think David handles netdev patches a bit differently for stable releases,
> I'd like to suggest this get included in the next batch for the 3.2 kernel.
> We've been seeing the bug this patch fixes in Fedora for quite a while now.
Hard to believe this bug lasted so long...
next prev parent reply other threads:[~2012-02-16 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329063403.1449.14.camel@localhost.localdomain>
[not found] ` <CA+5PVA52+0vOMF6+tvMPkgzhdTKJRQnrjD4FfVmBZs0TMDJ5cg@mail.gmail.com>
2012-02-14 7:36 ` NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out Eric Dumazet
2012-02-16 4:34 ` Eric Dumazet
2012-02-16 6:13 ` Thomas Meyer
2012-02-16 6:18 ` Eric Dumazet
2012-02-16 6:23 ` Thomas Meyer
2012-02-16 6:43 ` [PATCH] atl1c: dont use highprio tx queue Eric Dumazet
2012-02-16 12:36 ` Josh Boyer
2012-02-16 13:12 ` Eric Dumazet [this message]
2012-02-19 23:59 ` David Miller
2012-02-16 7:09 ` NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out Huang, Xiong
2012-02-21 17:56 ` Thomas Meyer
2012-02-21 18:14 ` Eric Dumazet
2012-02-24 19:20 ` Eric Dumazet
2012-02-25 9:52 ` Thomas Meyer
2012-06-06 0:38 ` Jonathan Nieder
2012-06-07 12:37 ` Thomas Meyer
2012-06-07 12:52 ` Eric Dumazet
2012-06-07 21:30 ` Huang, Xiong
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=1329397953.9395.0.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=jcliburn@gmail.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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