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 5D01F427E1; Mon, 20 Mar 2023 12:50:49 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0334940A7F; Mon, 20 Mar 2023 12:50:49 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id AED65406BC for ; Mon, 20 Mar 2023 12:50:47 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 440CB5C013B; Mon, 20 Mar 2023 07:50:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 20 Mar 2023 07:50:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1679313046; x=1679399446; bh=05naw09szzEz5B958dyuCXBdqk1EUYaNniR mrJkJ9G4=; b=o6ZSdCvKX81X+YMOzmny0Zn7Cgk81uXdlIjDtzMOHGiXk+i7ejG vk7Z3BW8BZbFQYApDZzCUAO0/dKoP579RZeRvrEGO26BuUR0KpLQbjalDJ7eoZVO rZOugR3efIKPEuJIorIQVH2HDDY3pHwD/N8ZTJSTpHgI9Tg8SbNE4pXHeFvYFBZ+ PiUXw1IuRamWyZG3HbKuxmzkr6qS4Ikj2tCjyAY6kbGnfftuQ4AcJBU/KABFu5S/ P/3dFGvzu6Gcz4+z4ydsHO0ra2zqQCZcglqei66nOqXt/OXi3UuyLNS29fzaM08W l3I4SE1SLyWwVUA2cCwizI9kRzFrKNxLrsg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1679313046; x=1679399446; bh=05naw09szzEz5B958dyuCXBdqk1EUYaNniR mrJkJ9G4=; b=Qbn4fS3Wbj3/+x3T31z2xVhuioVWaa1D/s3owh9V9Q6mNTc01DB 46YCT5Hzqr8m273edggEwvD3H5z4wVMP3GJfm8MlXSs3SZvkBIamSbilrQSFI4g0 t+8Kawv+6hgkW+QqNubX9qlCW7nuZtDDOTM3zjqAgyGFH/r0C4tqW6fNqynfrxX+ gAZEHKa7YYHV0F3D/rMP8LwEV+Yw2DKrc00MyinJb9Kp0UY5tGBpsZ4MuZOwlhbX O3LLmmbwWAweVoYRsrbnaC8W99RMybZVMllYBcee5dmpEZvws8UgEZK9qFTgeZuZ Fi8L4oBt/jZ+6Adf/55LrKeUlsK1z0ErXGg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdefkedgfedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpefftdeuhfehvdekleelveffvdelhfelhedvgedtvddvudeuieev tdfgjedvudegfeenucffohhmrghinhepughpughkrdhorhhgnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Mar 2023 07:50:44 -0400 (EDT) From: Thomas Monjalon To: "J.J. Martzki" Cc: dev@dpdk.org, stephen@networkplumber.org, konstantin.ananyev@huawei.com, Ruifeng Wang , Konstantin Ananyev Subject: Re: [PATCH v5] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap Date: Mon, 20 Mar 2023 12:50:43 +0100 Message-ID: <3559438.hdfAi7Kttb@thomas> In-Reply-To: <91770103-3420-e248-5727-8ef5df4f4970@yandex.ru> References: <20230312062021.7349-1-mars14850@gmail.com> <20230314142038.23436-1-mars14850@gmail.com> <91770103-3420-e248-5727-8ef5df4f4970@yandex.ru> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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 16/03/2023 01:58, Konstantin Ananyev: > 14/03/2023 14:20, J.J. Martzki =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > The library libpcap has their function 'bpf_validate' either so there w= ould > > be a multiple definition issue when linking with librte_bpf.a and libpc= ap.a > > statically (Same as http://dpdk.org/patch/52631). So just rename the > > function names to avoid such issue. > >=20 > > Signed-off-by: J.J. Martzki >=20 > Acked-by: Konstantin Ananyev Applied, thanks.