From: David Vrabel <david.vrabel@citrix.com>
To: Liang Li <liang.z.li@intel.com>, <linux-kernel@vger.kernel.org>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
<konrad.wilk@oracle.com>, <boris.ostrovsky@oracle.com>,
<andrew.bennieston@citrix.com>, <wei.liu2@citrix.com>,
<davem@davemloft.net>
Subject: Re: [PATCH] xen-netfront: Remove the meaningless code
Date: Fri, 26 Jun 2015 16:15:18 +0100 [thread overview]
Message-ID: <558D6C86.4040802@citrix.com> (raw)
In-Reply-To: <1435360646-7831-1-git-send-email-liang.z.li@intel.com>
On 27/06/15 00:17, Liang Li wrote:
> The function netif_set_real_num_tx_queues() will return -EINVAL if
> the second parameter < 1, so call this function with the second
> parameter set to 0 is meaningless.
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
David
next prev parent reply other threads:[~2015-06-26 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 23:17 [PATCH] xen-netfront: Remove the meaningless code Liang Li
2015-06-26 15:15 ` David Vrabel [this message]
2015-06-28 23:49 ` 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=558D6C86.4040802@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.bennieston@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=konrad.wilk@oracle.com \
--cc=liang.z.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).