patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Nikhil Rao <nikhil.rao@intel.com>,
	thomas@monjalon.net, dev@dpdk.org, erik.g.carrillo@intel.com,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 1/2] test: fix event timer compiler warning
Date: Fri, 28 Sep 2018 16:06:42 +0530	[thread overview]
Message-ID: <20180928103641.GB2152@jerin> (raw)
In-Reply-To: <20180927110855.GA19604@bricha3-MOBL.ger.corp.intel.com>

-----Original Message-----
> Date: Thu, 27 Sep 2018 12:08:56 +0100
> From: Bruce Richardson <bruce.richardson@intel.com>
> To: Nikhil Rao <nikhil.rao@intel.com>
> CC: thomas@monjalon.net, jerin.jacob@caviumnetworks.com, dev@dpdk.org,
>  erik.g.carrillo@intel.com, stable@dpdk.org
> Subject: Re: [PATCH v2 1/2] test: fix event timer compiler warning
> User-Agent: Mutt/1.10.1 (2018-07-13)
> 
> 
> On Thu, Sep 27, 2018 at 11:16:14AM +0530, Nikhil Rao wrote:
> > Limit the number of objects passed to rte_mempool_put_bulk()
> > to the size of the object table. This fix eliminates a compiler
> > warning (array-bounds) triggered when the march command line
> > parameter to gcc is set to nehalem.
> >
> > Fixes: d1f3385d0076 ("test: add event timer adapter auto-test")
> > Cc: erik.g.carrillo@intel.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied to dpdk-next-eventdev/master. Thanks.

      reply	other threads:[~2018-09-28 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1536155732-155032-1-git-send-email-nikhil.rao@intel.com>
2018-09-27  5:46 ` Nikhil Rao
2018-09-27 11:08   ` Bruce Richardson
2018-09-28 10:36     ` Jerin Jacob [this message]

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=20180928103641.GB2152@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=nikhil.rao@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).