DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Brian Dooley <brian.dooley@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 00/11] add missing C++ guards
Date: Tue, 15 Feb 2022 17:32:03 +0000	[thread overview]
Message-ID: <Ygvjk7wGIgZYArZe@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220215170817.662136-1-brian.dooley@intel.com>

On Tue, Feb 15, 2022 at 05:08:06PM +0000, Brian Dooley wrote:
> Public header files were missing 'extern "C"' guards.
> This set adds them in.
> 
> Brian Dooley (11):
>   eal: fix missing C++ guards
>   telemetry: fix missing C++ guards
>   ethdev: fix missing C++ guards
>   metrics: fix missing C++ guards
>   acl: fix missing C++ guards
>   compressdev: fix missing C++ guards
>   eventdev: fix missing C++ guards
>   kni: fix missing C++ guards
>   vhost: fix missing C++ guards
>   bpf: fix missing C++ guards
>   cryptodev: fix missing C++ guards
> 

Good cleanup to have for compatibility.

Series-Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  parent reply	other threads:[~2022-02-15 17:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 17:08 Brian Dooley
2022-02-15 17:08 ` [PATCH 01/11] eal: fix " Brian Dooley
2022-02-15 17:08 ` [PATCH 02/11] telemetry: " Brian Dooley
2022-02-15 17:08 ` [PATCH 03/11] ethdev: " Brian Dooley
2022-02-15 17:08 ` [PATCH 04/11] metrics: " Brian Dooley
2022-02-15 17:08 ` [PATCH 05/11] acl: " Brian Dooley
2022-02-15 17:08 ` [PATCH 06/11] compressdev: " Brian Dooley
2022-02-15 17:08 ` [PATCH 07/11] eventdev: " Brian Dooley
2022-02-15 17:08 ` [PATCH 08/11] kni: " Brian Dooley
2022-02-15 17:08 ` [PATCH 09/11] vhost: " Brian Dooley
2022-02-15 17:08 ` [PATCH 10/11] bpf: " Brian Dooley
2022-02-15 17:08 ` [PATCH 11/11] cryptodev: " Brian Dooley
2022-02-15 17:32 ` Bruce Richardson [this message]
2022-02-16 15:14 ` [PATCH v2 00/11] add " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 01/11] eal: fix " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 02/11] telemetry: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 03/11] ethdev: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 04/11] metrics: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 05/11] acl: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 06/11] compressdev: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 07/11] eventdev: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 08/11] kni: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 09/11] vhost: " Brian Dooley
2022-02-17  7:50     ` Xia, Chenbo
2022-02-16 15:14   ` [PATCH v2 10/11] bpf: " Brian Dooley
2022-02-16 15:14   ` [PATCH v2 11/11] cryptodev: " Brian Dooley
2022-02-17  8:00 ` [PATCH 00/11] add " Tyler Retzlaff
2022-02-22 14:02   ` 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=Ygvjk7wGIgZYArZe@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=brian.dooley@intel.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).