From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: jeffrey.t.kirsher@intel.com
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] e1000e: Remove duplicate assignment of default rx/tx ring size
Date: Tue, 21 May 2013 00:24:28 +0800 [thread overview]
Message-ID: <20130520162428.GA18520@weiyang.vnet.ibm.com> (raw)
In-Reply-To: <5199EECC.8040900@gmail.com>
On Mon, May 20, 2013 at 02:37:16AM -0700, Jeff Kirsher wrote:
>On 05/20/2013 01:15 AM, Wei Yang wrote:
>> tx_ring/rx_ring size is assigned in function e1000_alloc_queues(), which is
>> called by e1000_sw_init() in the early stage of e1000_probe().
>>
>> This patch just remove the duplicate assignment of this default ring size
>> value.
>>
>> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
>> Reviewed-by: Gavin Shan <shangw@linux.vnet.ibm.com>
>> Reviewed-by: Da Yu Qiu <qiudayu@cn.ibm.com>
>> ---
>> drivers/net/ethernet/intel/e1000e/netdev.c | 4 ----
>> 1 files changed, 0 insertions(+), 4 deletions(-)
>Thanks, I have added the patch to my queue for e1000e.
Thanks~
>
--
Richard Yang
Help you, Help me
next prev parent reply other threads:[~2013-05-20 16:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 8:15 [PATCH 0/4] trivial clean up for e1000e driver Wei Yang
2013-05-20 8:15 ` [PATCH 1/4] e1000e: Remove duplicate assignment of default rx/tx ring size Wei Yang
2013-05-20 9:37 ` Jeff Kirsher
2013-05-20 16:24 ` Wei Yang [this message]
2013-05-20 8:15 ` [PATCH 2/4] e1000e: Use marco instead of digit for defining e1000_rx_desc_packet_split Wei Yang
2013-05-20 9:37 ` Jeff Kirsher
2013-05-20 16:24 ` Wei Yang
2013-05-20 8:15 ` [PATCH 3/4] e1000e: Calculate the desc_len based on adapter type Wei Yang
2013-05-20 9:37 ` Jeff Kirsher
2013-05-20 16:25 ` Wei Yang
2013-08-22 10:57 ` Jeff Kirsher
2013-08-22 14:26 ` Wei Yang
2013-05-20 8:15 ` [PATCH 4/4] e1000e: Not initialize the e1000_ps_page array when packet-split is not used Wei Yang
2013-05-20 9:38 ` Jeff Kirsher
2013-05-20 16:25 ` Wei Yang
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=20130520162428.GA18520@weiyang.vnet.ibm.com \
--to=weiyang@linux.vnet.ibm.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@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).