DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: konstantin.ananyev@intel.com, bruce.richardson@intel.com
Subject: [dpdk-dev] [PATCH v2 2/2] builtools: remove build flag for header includes check
Date: Thu,  4 Feb 2021 11:05:20 +0100	[thread overview]
Message-ID: <20210204100520.15414-2-david.marchand@redhat.com> (raw)
In-Reply-To: <20210204100520.15414-1-david.marchand@redhat.com>

Previous patch just removes the last case of direct inclusion of the
generic/ headers.

Signed-off-by: David Marchand <david.marchand@redhat.com>
---
 buildtools/chkincs/meson.build | 1 -
 1 file changed, 1 deletion(-)

diff --git a/buildtools/chkincs/meson.build b/buildtools/chkincs/meson.build
index f345e87551..f28cfd3cd4 100644
--- a/buildtools/chkincs/meson.build
+++ b/buildtools/chkincs/meson.build
@@ -17,7 +17,6 @@ gen_c_files = generator(gen_c_file_for_header,
 	arguments: ['@INPUT@', '@OUTPUT@'])
 
 cflags = machine_args
-cflags += '-Wno-unused-function' # needed if we include generic headers
 cflags += '-DALLOW_EXPERIMENTAL_API'
 
 sources = files('main.c')
-- 
2.23.0


  reply	other threads:[~2021-02-04 10:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 20:33 [dpdk-dev] [PATCH] mbuf: remove unneeded EAL header include David Marchand
2021-02-01  7:51 ` Ruifeng Wang
2021-02-04 10:05 ` [dpdk-dev] [PATCH v2 1/2] mbuf: remove unneeded atomic " David Marchand
2021-02-04 10:05   ` David Marchand [this message]
2021-02-04 10:26     ` [dpdk-dev] [PATCH v2 2/2] builtools: remove build flag for header includes check Bruce Richardson
2021-02-05 18:48       ` Thomas Monjalon
2021-02-04 13:35   ` [dpdk-dev] [PATCH v2 1/2] mbuf: remove unneeded atomic header include Andrew Rybchenko

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=20210204100520.15414-2-david.marchand@redhat.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    /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).