From: David Miller <davem@davemloft.net>
To: franco@lastsummer.de
Cc: Brandeburg@host64.kissl.de, jesse.brandeburg@intel.com,
netdev@vger.kernel.org, Allan@host64.kissl.de,
bruce.w.allan@intel.com
Subject: Re: [net-next-2.6 PATCH] e1000e: do not modify tx queue len on link speed change
Date: Thu, 04 Mar 2010 00:41:28 -0800 (PST) [thread overview]
Message-ID: <20100304.004128.236847399.davem@davemloft.net> (raw)
In-Reply-To: <20100303143137.0BCA01220127@host64.kissl.de>
From: franco@lastsummer.de
Date: Wed, 3 Mar 2010 15:31:37 +0100 (CET)
> e1000e would try to set appropriate values of tx_queue_len for
> negotiated
> link speeds overwriting the already set configuration of tx_queue_len in
> the process. This removes all lines touching tx_queue_len from the
> driver.
>
> Signed-off-by: Franco Fichtner <franco@lastsummer.de>
Intel folks, you got this?
next prev parent reply other threads:[~2010-03-04 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 14:31 [net-next-2.6 PATCH] e1000e: do not modify tx queue len on link speed change franco
2010-03-04 8:41 ` David Miller [this message]
2010-03-04 14:41 ` Jeff Kirsher
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=20100304.004128.236847399.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Allan@host64.kissl.de \
--cc=Brandeburg@host64.kissl.de \
--cc=bruce.w.allan@intel.com \
--cc=franco@lastsummer.de \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@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).