DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Akhil Goyal <gakhil@marvell.com>,
	"Ashish Gupta" <ashish.gupta@marvell.com>,
	Fan Zhang <fanzhang.oss@gmail.com>, Kai Ji <kai.ji@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: [PATCH v2 0/2] compressdev: fix end of list enums conflict
Date: Wed, 1 Feb 2023 17:35:29 +0200	[thread overview]
Message-ID: <20230201153531.912219-1-michaelba@nvidia.com> (raw)
In-Reply-To: <20230101134720.1709991-1-michaelba@nvidia.com>

Handle the conflict about which enum value is used as end of list.

v2: add patch to remove useless list end enums.

Michael Baum (2):
  compressdev: fix end of comp PMD list macro conflict
  compressdev: remove useless list end enums

 drivers/compress/mlx5/mlx5_compress.c        | 4 +---
 drivers/compress/qat/dev/qat_comp_pmd_gen1.c | 2 +-
 drivers/compress/qat/dev/qat_comp_pmd_gen4.c | 2 +-
 lib/compressdev/rte_comp.h                   | 2 --
 lib/compressdev/rte_compressdev.h            | 2 +-
 5 files changed, 4 insertions(+), 8 deletions(-)

-- 
2.25.1


  parent reply	other threads:[~2023-02-01 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 13:47 [PATCH] compressdev: fix end of comp PMD list macro conflict Michael Baum
2023-01-25  6:53 ` Michael Baum
2023-01-30 19:30 ` [EXT] " Akhil Goyal
2023-01-31  8:23   ` Akhil Goyal
2023-02-01 13:19     ` Akhil Goyal
2023-02-01 13:29       ` Michael Baum
2023-02-01 14:02         ` Akhil Goyal
2023-02-01 15:35 ` Michael Baum [this message]
2023-02-01 15:35   ` [PATCH v2 1/2] " Michael Baum
2023-02-01 15:35   ` [PATCH v2 2/2] compressdev: remove useless list end enums Michael Baum
2023-02-05 17:24   ` [EXT] [PATCH v2 0/2] compressdev: fix end of list enums conflict Akhil Goyal

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=20230201153531.912219-1-michaelba@nvidia.com \
    --to=michaelba@nvidia.com \
    --cc=ashish.gupta@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=matan@nvidia.com \
    --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).