From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] 20.05-rc1 fixes for OVS
Date: Tue, 28 Apr 2020 11:53:08 +0200 [thread overview]
Message-ID: <CAJFAV8zFmkGKP4Aff5LvbLH7z7R_jFG1+OXZNwBeuLS7z1fjGQ@mail.gmail.com> (raw)
In-Reply-To: <20200427132341.27681-1-david.marchand@redhat.com>
On Mon, Apr 27, 2020 at 3:24 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Couple of fixes caught while checking OVS integration.
>
> David Marchand (3):
> ring: fix build with -Wswitch-enum
> eal: fix typo in endian conversion macros
> ethdev: fix build warning on 64-bit value
>
> lib/librte_eal/include/generic/rte_byteorder.h | 6 +++---
> lib/librte_ethdev/rte_flow.h | 2 +-
> lib/librte_ring/rte_ring_peek.h | 8 ++++++++
> 3 files changed, 12 insertions(+), 4 deletions(-)
>
Series applied.
--
David Marchand
prev parent reply other threads:[~2020-04-28 9:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 13:23 David Marchand
2020-04-27 13:23 ` [dpdk-dev] [PATCH 1/3] ring: fix build with -Wswitch-enum David Marchand
2020-04-27 14:55 ` Ananyev, Konstantin
2020-04-27 13:23 ` [dpdk-dev] [PATCH 2/3] eal: fix typo in endian conversion macros David Marchand
2020-04-27 13:35 ` Bruce Richardson
2020-04-27 13:23 ` [dpdk-dev] [PATCH 3/3] ethdev: fix build warning on 64-bit value David Marchand
2020-04-27 13:33 ` Andrew Rybchenko
2020-04-27 13:34 ` Bruce Richardson
2020-04-27 13:36 ` David Marchand
2020-04-27 13:46 ` Ananyev, Konstantin
2020-04-27 14:00 ` David Marchand
2020-04-27 14:07 ` Ferruh Yigit
2020-04-27 14:12 ` David Marchand
2020-04-27 14:14 ` Ferruh Yigit
2020-04-28 9:27 ` Thomas Monjalon
2020-05-06 14:37 ` Morten Brørup
2020-04-27 13:39 ` Andrew Rybchenko
2020-04-27 13:40 ` David Marchand
2020-04-27 13:43 ` Bruce Richardson
2020-04-28 9:53 ` David Marchand [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=CAJFAV8zFmkGKP4Aff5LvbLH7z7R_jFG1+OXZNwBeuLS7z1fjGQ@mail.gmail.com \
--to=david.marchand@redhat.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).