From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1C1E145B94; Mon, 21 Oct 2024 18:05:04 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C68E740285; Mon, 21 Oct 2024 18:05:03 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 928F740263 for ; Mon, 21 Oct 2024 18:05:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1729526701; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ni0upj8DHV2wzEOiJNqTVxHXjl8D/EbYQdrmxwf5zP8=; b=PEudc7uhvub7lO1rlwSsOQjCZ0vKjxSeXhS9lUyg8TC/FmkjKNVqC87N6uBpGH6V0Tixyh 6pt2Kmx+nSuNNVxPEn/AcHJI8ADogr+DmiT2x9sgJOkhAzeTJ9uwbsgA7M7qia5tAsH6uO OME0/WVOqvfx7nBhXdRL3GnSPZlX20Q= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-150-nbey9vbaMb2_iHxaGVzScQ-1; Mon, 21 Oct 2024 12:04:58 -0400 X-MC-Unique: nbey9vbaMb2_iHxaGVzScQ-1 Received: from mx-prod-int-04.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-04.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id DA049195608B; Mon, 21 Oct 2024 16:04:56 +0000 (UTC) Received: from dmarchan.redhat.com (unknown [10.45.224.57]) by mx-prod-int-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 157EE19560AA; Mon, 21 Oct 2024 16:04:54 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: thomas@monjalon.net, bruce.richardson@intel.com, ktraynor@redhat.com Subject: [PATCH v3 0/4] Enhance headers check Date: Mon, 21 Oct 2024 18:04:43 +0200 Message-ID: <20241021160447.3538245-1-david.marchand@redhat.com> In-Reply-To: <20241015121046.2556695-1-david.marchand@redhat.com> References: <20241015121046.2556695-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.40 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org We currently check that exported headers are fine with -DALLOW_EXPERIMENTAL_API and -DALLOW_INTERNAL_API. Such a check won't catch issues when build is broken in the absence of those flags, which is the common case for applications consuming DPDK. This series adds more coverage. -- David Marchand Changes since v2: - rebased on rc1, - added check when calling rte_bitset without ALLOW_EXPERIMENTAL_API, - added checks (and fixes) on driver specific headers, David Marchand (4): bitset: fix build for GCC without experimental API buildtools/chkincs: check headers with stable API only bus/ifpga: use C linkage where appropriate in driver header buildtools/chkincs: check driver specific headers buildtools/chkincs/meson.build | 30 +++++- drivers/bus/ifpga/bus_ifpga_driver.h | 8 +- drivers/meson.build | 1 + lib/eal/include/rte_bitset.h | 132 +++++++++++++++++++++++++++ 4 files changed, 165 insertions(+), 6 deletions(-) -- 2.46.2