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 C4AFA41E1D; Mon, 13 Mar 2023 16:54:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ABC5040F18; Mon, 13 Mar 2023 16:54:40 +0100 (CET) Received: from mail-pg1-f170.google.com (mail-pg1-f170.google.com [209.85.215.170]) by mails.dpdk.org (Postfix) with ESMTP id 0D4FB406BC for ; Mon, 13 Mar 2023 16:54:39 +0100 (CET) Received: by mail-pg1-f170.google.com with SMTP id p6so7208270pga.0 for ; Mon, 13 Mar 2023 08:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1678722878; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=0kf3qwqosOUAHsrkYTn+lx1BCSxFJrj5Mdq+lffu/+8=; b=BaxQ2sVMjsDzR1LulSd5t454uSO7r/ZdRTKkGjeVNiVOnkepfgqmWVx+liSxjyX0xL ksKiUIYoYFleDU0gheEffHXGtnXVg/l9weoJdr/d5ZQEF/Elf8VG5M7H3kz6Ko6GHCtb ouuSlQYeufrIewld9ppmBdFikJ9l3vUXzmmmbZdUemMNlqWbqxETgGNep/hIFh9HqSGC wWxoOJXU6pKZAdkoWp0fgIm0pKrVfkI2eSR58HDd9Szau3icyTAIWmwmYwFxKBVhRyxs uwG5qp9isTaiZqc8vnWOrcCDkSvqNciGW6jUu0rLLvjB9LTW/k9zkM921KwHF1Qg1fv/ Xadw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678722878; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=0kf3qwqosOUAHsrkYTn+lx1BCSxFJrj5Mdq+lffu/+8=; b=wElyxu/jWb7E0PAK003Nx4lBK/PbomvgPh0MvtiULjU9uOI1ClXb52aDk0Q2H+NNi3 4HNSwtGVpsEPN49Kr83IycZoFyx5DJSICmAgOD9bKarls+CDDV6Q2boLDonG2MXxT76t 4KNDMnYdqYxwkTMkLxbsoPNC/zjqD2rgtzGYw74ldOtintd88Mr0IDTkEsQO8LEoTBQO DvnqbKnFHaji9lrLZpWdQoK95IXwNOWDd5c6pQrKbhAjBHieQJeVPY6RBQm9J4MTkPA5 OEJhS5jGqXTX7J7JSxVAP6gPfi4TeOd73/SVb1bqptfZsrreOfL+JP/4kUXhcvh4rr49 GYXQ== X-Gm-Message-State: AO0yUKXheLphgiqyFEykpjvwMb4VJW4ELey7SGFoEjZTQ/USTx+BNbE5 fiRjA6eQqLPh0blB5e+aivj8qA== X-Google-Smtp-Source: AK7set93WigD7UUTum8kX5wIxEIcb9SZg8v7SRGIuIEbPXSQYdajdePmj7NLZtwan4DZlYMMv0yH6A== X-Received: by 2002:a62:1dc7:0:b0:622:749a:b9de with SMTP id d190-20020a621dc7000000b00622749ab9demr6062352pfd.27.1678722878230; Mon, 13 Mar 2023 08:54:38 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id 19-20020a630c53000000b004f2c088328bsm155677pgm.43.2023.03.13.08.54.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Mar 2023 08:54:38 -0700 (PDT) Date: Mon, 13 Mar 2023 08:54:36 -0700 From: Stephen Hemminger To: "J.J. Martzki" Cc: Konstantin Ananyev , dev@dpdk.org, thomas@monjalon.net, Ruifeng Wang Subject: Re: [PATCH v4] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap Message-ID: <20230313085436.25a58d6b@hermes.local> In-Reply-To: References: <20230306154216.41154-1-mars14850@gmail.com> <20230312062021.7349-1-mars14850@gmail.com> <948b18da-3e41-c65c-7d47-b49ba6a4d810@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Mon, 13 Mar 2023 22:55:34 +0800 "J.J. Martzki" wrote: > I've read the libbpf code again and I found some other functions with > pure 'bpf_' prefix. Should we rename all the functions whose names > start with pure 'bpf_'? Yes, all visible (ie non-static) functions should use a DPDK style prefix.