From: Bruce Richardson <bruce.richardson@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org, Nelson Escobar <neescoba@cisco.com>
Subject: Re: [dpdk-dev] [PATCH] enic: prevent segfaults when allocating too many TX or RX queues
Date: Tue, 22 Mar 2016 16:46:30 +0000 [thread overview]
Message-ID: <20160322164630.GD20448@bricha3-MOBL3> (raw)
In-Reply-To: <1458254998-4336-1-git-send-email-johndale@cisco.com>
On Thu, Mar 17, 2016 at 03:49:58PM -0700, John Daley wrote:
> From: Nelson Escobar <neescoba@cisco.com>
>
> Add checks to make sure we don't try to allocate more tx or rx queues
> than we support.
>
> Signed-off-by: Nelson Escobar <neescoba@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>
Better to use the word fix in the title to indicate this is a bug-fix. Also missing
a fixes line of:
Fixes: fefed3d1e62c ("enic: new driver")
Will fix this up on apply.
/Bruce
next prev parent reply other threads:[~2016-03-22 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 22:49 John Daley
2016-03-22 16:46 ` Bruce Richardson [this message]
2016-03-22 16:47 ` Bruce Richardson
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=20160322164630.GD20448@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.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).