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=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS autolearn=no 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 A0077C388F3 for ; Mon, 30 Sep 2019 22:58:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 714712086A for ; Mon, 30 Sep 2019 22:58:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="pvymu7Ve" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731919AbfI3W6s (ORCPT ); Mon, 30 Sep 2019 18:58:48 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:45382 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731685AbfI3W6r (ORCPT ); Mon, 30 Sep 2019 18:58:47 -0400 Received: by mail-qt1-f194.google.com with SMTP id c21so19167533qtj.12; Mon, 30 Sep 2019 15:58:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cvCTcx43JDg1o6KPY5fDSJTzdGhnKOviIKAIHHSnoeI=; b=pvymu7VeESp4BaH6p35MroG5OK7PLwJMqW7vJJx0W8ajfBzAjnZFz1GOe+TtSVWS6Y Ft74dgo8akgHikqAMHkRh+dKShlc4GVKBhIg2tBN3ef8pUsE59YAWoq1kCzkqv0eqTmN xvSFrYXrKs88bwLf5ZGa2tExHnVmtVG0OiX6eUxAdGwXiBq0BRpemcoKvSpR74EhKvmx 9sM4yCgwtG8tLL6RVOnpBKShsZ3tudjg5N5KDRsmdQho/QawGWSmETd/B6vfz9G5P1K8 cAXxItfc4cwjgTGKEwER8D7jhZ9ql+kRPbC4L+sr81iA9yfIzzhv3cjCOtJTyaIi8Wga Dg+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cvCTcx43JDg1o6KPY5fDSJTzdGhnKOviIKAIHHSnoeI=; b=Zg+cEM8JBcXxtcfLKZOB8TsLE4YBGhyYhd3OPHAWxmeEOvg07a5xzNsQfg1F308olR Tm8mu665H4tWyZzC2dCkLiP7H/4WffKovqgPG013dR1J39wk4E8E+3GAHIEFTGmVHonh V5VUpwJX9380K9MxEEl6sKZ7DopEt7ebylTdWSk0nzrZEG08NfNIa7SjYXp+8POSxAgG 1/zgtSbotXMrbpLWxmu2TAfH3VGARE2Ok7/MnKsaOvXdY0GRcYMnEUuh+8pXLCwwGLAs Hhq9ShH+jQWVyHu19YMv1uUpwpci+4pY0ioN9Ncz90Z3LM1koAH3GbKSMJs08tlW+uC0 mRWQ== X-Gm-Message-State: APjAAAW+XkkLMhRSY4bsQqQRyT1m+FAEUkgNhrQ3K6HGtkE4ngTrME+D yvJeSz0s81piMIEFnK+lzNDfmsS3KSxOfBnD/OE= X-Google-Smtp-Source: APXvYqz8QjXfyMdU7bHG/VQoO+Hok1DHYk+5fo6q/VjSYjeEHG1vou/JweDL+45RxpohymsVQgM+xKYTCZjNtjioAs0= X-Received: by 2002:a05:6214:114a:: with SMTP id b10mr22523228qvt.150.1569884326168; Mon, 30 Sep 2019 15:58:46 -0700 (PDT) MIME-Version: 1.0 References: <20190930185855.4115372-1-andriin@fb.com> <20190930185855.4115372-3-andriin@fb.com> In-Reply-To: From: Andrii Nakryiko Date: Mon, 30 Sep 2019 15:58:35 -0700 Message-ID: Subject: Re: [PATCH bpf-next 2/6] libbpf: move bpf_helpers.h, bpf_endian.h into libbpf To: Song Liu Cc: Andrii Nakryiko , bpf , Networking , Alexei Starovoitov , Daniel Borkmann , Kernel Team Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Sep 30, 2019 at 3:55 PM Song Liu wrote: > > On Mon, Sep 30, 2019 at 1:43 PM Andrii Nakryiko wrote: > > > > Make bpf_helpers.h and bpf_endian.h official part of libbpf. Ensure they > > are installed along the other libbpf headers. > > > > Signed-off-by: Andrii Nakryiko > > Can we merge/rearrange 2/6 and 3/6, so they is a git-rename instead of > many +++ and ---? I arranged them that way because of Github sync. We don't sync selftests/bpf changes to Github, and it causes more churn if commits have a mix of libbpf and selftests changes. I didn't modify bpf_helpers.h/bpf_endian.h between those patches, so don't worry about reviewing contents ;) > > Thanks, > Song