From: Olivier Matz <olivier.matz@6wind.com>
To: Andy Green <andy@warmcat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 2/2] ring: fix sign conversion warning
Date: Mon, 16 Jul 2018 09:16:29 +0200 [thread overview]
Message-ID: <20180716071629.yavjmh6yztvfgrsk@platinum> (raw)
In-Reply-To: <152749822351.44120.16656625173859188832.stgit@localhost.localdomain>
On Mon, May 28, 2018 at 05:03:43PM +0800, Andy Green wrote:
> On gcc 5.4.0 / native aarch64 from Ubuntu 16.04:
>
> /home/agreen/lagopus/src/dpdk/build/include/rte_ring.h:
> In function '__rte_ring_do_dequeue':
> /home/agreen/lagopus/src/dpdk/build/include/rte_ring.h:
> 385:35: warning: conversion to 'int' from 'unsigned int'
> may change the sign of the result [-Wsign-conversion]
> n = __rte_ring_move_cons_head(r, is_sc, n, behavior,
> ^
>
> Signed-off-by: Andy Green <andy@warmcat.com>
> Fixes: e8ed5056c8 ("ring: remove signed type flip-flopping")
Acked-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2018-07-16 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 2:29 [dpdk-dev] [PATCH 0/2] dpdk header fixes for aarch64 Andy Green
2018-05-28 2:29 ` [dpdk-dev] [PATCH 1/2] ring: fix declaration after code Andy Green
2018-05-28 8:15 ` Gavin Hu
2018-05-28 8:46 ` Andy Green
2018-05-28 8:54 ` Gavin Hu
2018-05-28 2:29 ` [dpdk-dev] [PATCH 2/2] ring: fix sign conversion warning Andy Green
2018-05-28 9:03 ` [dpdk-dev] [PATCH v2 0/2] dpdk header fixes for aarch64 Andy Green
2018-05-28 9:03 ` [dpdk-dev] [PATCH v2 1/2] ring: fix declaration after code Andy Green
2018-07-16 7:15 ` Olivier Matz
2018-05-28 9:03 ` [dpdk-dev] [PATCH v2 2/2] ring: fix sign conversion warning Andy Green
2018-07-16 7:16 ` Olivier Matz [this message]
2018-07-26 13:30 ` [dpdk-dev] [PATCH v2 0/2] dpdk header fixes for aarch64 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=20180716071629.yavjmh6yztvfgrsk@platinum \
--to=olivier.matz@6wind.com \
--cc=andy@warmcat.com \
--cc=dev@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).