DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev@dpdk.org, Luca Boccassi <bluca@debian.org>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] meson: remove build warnings
Date: Tue, 26 Mar 2019 23:32:30 +0100	[thread overview]
Message-ID: <2783266.6LeuiB9IJV@xps> (raw)
In-Reply-To: <1bc7f7793e60adc4abd36568b346bdcf0569ba64.camel@debian.org>

19/03/2019 18:36, Luca Boccassi:
> On Tue, 2019-03-19 at 17:22 +0000, Jerin Jacob Kollanukkaran wrote:
> > From: Jerin Jacob <jerinj@marvell.com>
> > 
> > Remove the following warning by comparing string to string.
> > 
> > config/arm/meson.build:153: WARNING: Trying to compare values of
> > different types (list, str) using ==.
> > 
> > Fixes: c6e536e38437 ("build: add more implementers IDs and PNs for
> > ARM")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> 
> Acked-by: Luca Boccassi <bluca@debian.org>

Applied, thanks

  parent reply	other threads:[~2019-03-26 22:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 16:28 [dpdk-dev] [PATCH] " Jerin Jacob Kollanukkaran
2019-03-18 16:28 ` Jerin Jacob Kollanukkaran
2019-03-18 17:15 ` Luca Boccassi
2019-03-18 17:15   ` Luca Boccassi
2019-03-19  9:50   ` Bruce Richardson
2019-03-19  9:50     ` Bruce Richardson
2019-03-27 15:28     ` Aaron Conole
2019-03-27 15:28       ` Aaron Conole
2019-03-27 15:44       ` Luca Boccassi
2019-03-27 15:44         ` Luca Boccassi
2019-03-19 17:22 ` [dpdk-dev] [PATCH v2] " Jerin Jacob Kollanukkaran
2019-03-19 17:22   ` Jerin Jacob Kollanukkaran
2019-03-19 17:36   ` Luca Boccassi
2019-03-19 17:36     ` Luca Boccassi
2019-03-26 22:32     ` Thomas Monjalon [this message]
2019-03-26 22:32       ` Thomas Monjalon

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=2783266.6LeuiB9IJV@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.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).