From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-17.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BE654C636CA for ; Sun, 18 Jul 2021 19:37:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A6A2D61029 for ; Sun, 18 Jul 2021 19:37:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230502AbhGRTkD (ORCPT ); Sun, 18 Jul 2021 15:40:03 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:53384 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232869AbhGRTj5 (ORCPT ); Sun, 18 Jul 2021 15:39:57 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 46F1E1FF85; Sun, 18 Jul 2021 19:36:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1626637017; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4VE9wboOFBx1A8aW4S+ryH5vyFPrMvrAxG+rYAOecbI=; b=ukHRmbXDBEVbDHcM8eunsLDAOCZk5tNxG2yqo2wO+OmNccN+pO9QVa8fBvTTQ+h1/EaJe+ qsC1Me6BrCQHMrj/f3WSmmaTpkRy3BWLxX1oG5wrL3f/tcP4ZLSyMqvPiEb1Kzeuo4vzpa F7wuGKbvUdPQgRGF0k2/WVsElwduTII= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1626637017; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4VE9wboOFBx1A8aW4S+ryH5vyFPrMvrAxG+rYAOecbI=; b=P4Wce5HwkC9qDoGp1bzga35bz0KN5aO0WYhI+Y8CCVO4Vs+nvxKEGEASXw86rC2vKUtHP2 DJOa6+oJWTVjvIDA== Received: from kitsune.suse.cz (kitsune.suse.cz [10.100.12.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id AEAC5A3B83; Sun, 18 Jul 2021 19:36:56 +0000 (UTC) Date: Sun, 18 Jul 2021 21:36:55 +0200 From: Michal =?iso-8859-1?Q?Such=E1nek?= To: Daniel Borkmann Cc: bpf@vger.kernel.org, Alexei Starovoitov , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , =?iso-8859-1?Q?Bj=F6rn_T=F6pel?= , Magnus Karlsson , Jonathan Lemon , Paul Walmsley , Palmer Dabbelt , Albert Ou , "David S. Miller" , Jakub Kicinski , Jesper Dangaard Brouer , Nathan Chancellor , Nick Desaulniers , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-riscv@lists.infradead.org, clang-built-linux@googlegroups.com Subject: Re: [PATCH] libbpf: Remove from kernel tree. Message-ID: <20210718193655.GP24916@kitsune.suse.cz> References: <20210718065039.15627-1-msuchanek@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 18, 2021 at 09:04:16PM +0200, Daniel Borkmann wrote: > On 7/18/21 8:50 AM, Michal Suchanek wrote: > > libbpf shipped by the kernel is outdated and has problems. Remove it. > > > > Current version of libbpf is available at > > > > https://github.com/libbpf/libbpf > > > > Link: https://lore.kernel.org/bpf/b07015ebd7bbadb06a95a5105d9f6b4ed5817b2f.camel@debian.org/ > > Signed-off-by: Michal Suchanek > > NAK, I'm not applying any of this. If there are issues, then fix them. If They are fixed in the github version. > you would have checked tools/lib/bpf/ git history, you would have found > that libbpf is under active development in the upstream kernel tree and So is the github version. > you could have spared yourself this patch. You could have spared me a lot of problems if there was only one source for libbpf. Can't you BPF people agree on one place to develop the library? Thanks Michal