Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp2652268rwn; Fri, 9 Sep 2022 18:13:02 -0700 (PDT) X-Google-Smtp-Source: AA6agR71f/y6pqCItQ+AMwqK4H+/3Tbge7d01/X0yxwQwM827Ujk4pZc+7c770p8DuHePR1gBu8A X-Received: by 2002:a05:6402:1283:b0:44f:2daa:d423 with SMTP id w3-20020a056402128300b0044f2daad423mr10928247edv.52.1662772382606; Fri, 09 Sep 2022 18:13:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662772382; cv=none; d=google.com; s=arc-20160816; b=JBJANtoFZ+sDhCzrrSK/8k5lZ9k9Oxk1hYE/LwvdcVexja7UJD9hLN+uhvyWiw8YIE KYAB7RzyFGeUnLfDRXhUmnlPLUTsnkWdIc/RbMg/VP2vvUKW3tc3mQ9FYal/dcUAwLAi SX0tnel0mrcMUtg1PqHPYzt1RrnC50cM5OjLQ5YLSvmpI0HDJd28MswK4tE6FpDmxRBf aTVceokMg+uuTvdgwl6LN4IoCznTLOp+26qvd8d7/9+t1I2JSzb0CUe2Uuz+N0cOx4E1 dCF1hv7K6Ods6E5+ZbG5R1/HjmsBiFsvaYpBvFUagEuLjRgVpOiUpJGzxBe6Jm055fSQ 5FlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=JIgqb5b60C8SmDMIEm+s+7Z4AskuEzxdfRuYH/CGCZE=; b=yx7ch3ZAjS1OkxCEpi83ner8R+xjVAZH6SVxFGxGUFiCh44mVIq9KP6TBp/3JKbk5J ZJoy05ZAUzo3mmS7NonI3mcKKZopPmlDXfoOPWp2I2GNNLx3MkSe0PLNng5fBGIjwsXQ Dzpqnym7NzQDmCywRVDZBVcsMMWMv55Ef1ECns6IjKJf32nnMtX2nNUFyvsaVrav6Fos KDeKuk5JDhrCzGhmKMVQm6u0E6KuE5Ihswvricf9BwSNwDrqhc3CUe4a66eOJME1KaJO PQN0t3B5OoULR9BuwjIak3WFKu+ZUUMBoLwt+O2Y/T4+feIjLDZpAJpo0Isa4s9hZz/e N2zA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="KjT2/7h4"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bm5-20020a170906c04500b0077a5733ac08si1341524ejb.601.2022.09.09.18.12.37; Fri, 09 Sep 2022 18:13:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="KjT2/7h4"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229810AbiIJAoR (ORCPT + 99 others); Fri, 9 Sep 2022 20:44:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43286 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229690AbiIJAoO (ORCPT ); Fri, 9 Sep 2022 20:44:14 -0400 Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C8AC2FC652; Fri, 9 Sep 2022 17:44:12 -0700 (PDT) Received: by mail-ej1-x636.google.com with SMTP id gh9so7814272ejc.8; Fri, 09 Sep 2022 17:44:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=JIgqb5b60C8SmDMIEm+s+7Z4AskuEzxdfRuYH/CGCZE=; b=KjT2/7h4lMbloMYZZWErBlgfsEJzqgWBEH3BP6COYgwI1mG3PsjVp+CvvAs5Cz+fbS OXxEz0jUY3VZm2oZ4Ln5vXloM809c2PDIUI+tt1QraYNHo8jv1tWISzhWUxrosvYE5zZ L6slugx6ZYCXiGwX/eP+DCh1R4nawgR6mIS5sW1AU5aatw03k5VggnzF9F7WnIlSGGDz 0tcCVtZ9f3ZoFCayp6vAt/Po0HY36kQhZjhV3PtEv6JnkUNbRGN1piPxlQPrQcv7VzeQ SvArKEoN5SxR9+kAKX14haT6V5dM4KFnOQgktMq66mLNvdsLRU3k+xwGxiMgNN4NjVS0 oj9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=JIgqb5b60C8SmDMIEm+s+7Z4AskuEzxdfRuYH/CGCZE=; b=5tvJ8TXOAxmQJ/rYYrReJ1RY/Vi5AA2T64x9QLauyEsRNKadIMk4ql1+g6/iPyGhtl 52CRdNUhDSWlpXCHH25zlY3G3nVZs658/OAwiwRxZDiduivExsjdrGXP9vLydfdfGqX2 nh0S2vLfzbdExAyMOLMCXaBPT3emIQ4zlu98DUTBvVLCF4PLX03wsctTEBLKTv2FCO8A UOKkcg7mZItmiKR+SpDKFSFs828ivXlsX+PKRGZleqtsKGOE0jvr+10VMgCpgCtxQpeA GWD9T4KykYNa/xEtAMAKWxlDJT1ZtdAkk2qNVMKlx9U4WD3CUXHcKSI+ddkv6YH2zPXP 0keQ== X-Gm-Message-State: ACgBeo1Aw0OU2LDff8qHv+AiJO1PL59LrAxe9o1Jr4IY5pWic4EQytrA PJARIz5/L+PAIU+6AF4TCBG8V8bMM6ccvEnkqJA= X-Received: by 2002:a17:906:8454:b0:772:7b02:70b5 with SMTP id e20-20020a170906845400b007727b0270b5mr8878137ejy.114.1662770651341; Fri, 09 Sep 2022 17:44:11 -0700 (PDT) MIME-Version: 1.0 References: <94275aa1e5af4efea53f322f91b27380@huawei.com> In-Reply-To: <94275aa1e5af4efea53f322f91b27380@huawei.com> From: Andrii Nakryiko Date: Fri, 9 Sep 2022 17:44:00 -0700 Message-ID: Subject: Re: [PATCH v2] libbpf: Clean up legacy bpf maps declaration in bpf_helpers To: "Liuxin(EulerOS)" Cc: "andrii@kernel.org" , "daniel@iogearbox.net" , "ast@kernel.org" , "martin.lau@linux.dev" , "song@kernel.org" , "yhs@fb.com" , "john.fastabend@gmail.com" , "kpsingh@kernel.org" , "sdf@google.com" , "haoluo@google.com" , "jolsa@kernel.org" , "bpf@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "854182924@qq.com" <854182924@qq.com>, "Yanan (Euler)" , "Wuchangye (EulerOS)" , Xiesongyang , "zhudi (E)" , "kongweibin (A)" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 6, 2022 at 7:51 PM Liuxin(EulerOS) wrote: > > Legacy bpf maps declaration were no longer supported in Libbpf 1.0, so it was time to remove the definition of bpf_map_def in bpf_helpers.h. please make sure that commit log lines are wrapped at <80 characters > > LINK:[1] https://github.com/libbpf/libbpf/wiki/Libbpf:-the-road-to-v1.0 don't add "LINK", just two spaces and then [0] and then refer to it from the above as "supported in Libbpf 1.0 ([0])" > > Acked-by: Song Liu > Signed-off-by: Xin Liu space after name and before opening < is missing > --- > Changes in v2: > - Fix strange signatures > It looks good overall, but your patch doesn't apply. Please make sure you base it on top of bpf-next's master and you use git send-email which won't clobber the patch. Thanks. > V1: https://lore.kernel.org/bpf/CAPhsuW7Em6q5hqiKWEZpJOaU5DTrZE+BPPHq+Chyz0-+-yQ_ZA@mail.gmail.com/T/#t > > tools/lib/bpf/bpf_helpers.h | 12 ------------ > 1 file changed, 12 deletions(-) > > diff --git a/tools/lib/bpf/bpf_helpers.h b/tools/lib/bpf/bpf_helpers.h index 867b73483..9cad13e7f 100644 > --- a/tools/lib/bpf/bpf_helpers.h > +++ b/tools/lib/bpf/bpf_helpers.h > @@ -167,18 +167,6 @@ bpf_tail_call_static(void *ctx, const void *map, const __u32 slot) } #endif > > -/* > - * Helper structure used by eBPF C program > - * to describe BPF map attributes to libbpf loader > - */ > -struct bpf_map_def { > - unsigned int type; > - unsigned int key_size; > - unsigned int value_size; > - unsigned int max_entries; > - unsigned int map_flags; > -} __attribute__((deprecated("use BTF-defined maps in .maps section"))); > - > enum libbpf_pin_type { > LIBBPF_PIN_NONE, > /* PIN_BY_NAME: pin maps by name (in /sys/fs/bpf by default) */ > -- > 2.33.0