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=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 C819BC432C3 for ; Wed, 27 Nov 2019 16:39:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9BAD42073F for ; Wed, 27 Nov 2019 16:39:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="REPG81Qt" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727165AbfK0Qjm (ORCPT ); Wed, 27 Nov 2019 11:39:42 -0500 Received: from mail-lf1-f67.google.com ([209.85.167.67]:33556 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726514AbfK0Qjm (ORCPT ); Wed, 27 Nov 2019 11:39:42 -0500 Received: by mail-lf1-f67.google.com with SMTP id d6so17720592lfc.0; Wed, 27 Nov 2019 08:39:41 -0800 (PST) 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=vmkegaf4vZvX2ziqVB5RPleLu7JAiT7hE0cpq3SxoSQ=; b=REPG81Qtq3lNOAL+04c29Gqfhs6hoxI9x9Bmws8ZTR3V99PKkY+OF1st8X4uBP4+EC i24A2tCrAPpdRJ+2h2zsAB18U2WiSgrWA67/0Mx5A+4Qr2CYxIKKq0l5eALsYfy16w2d hOJPxdff+EgcnL/vbeY1eGmbZNZjso+4Zz8MPUjrHrKA5Luwa+z9bh/FnOr7RsaNOCLW O6W2Ec9mjDdyuW/LS9UKPdipoMwDZoYqrjOU20jx/n96jpZNQO7ow5jyxT1Hab1mLH4M hBFZVxl40aCaqofV7YX/x9hJoisKCt52V6aN5SjuehrqOAewrinJBS9DIxH95sN0E3iY V51Q== 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=vmkegaf4vZvX2ziqVB5RPleLu7JAiT7hE0cpq3SxoSQ=; b=s1fW+od24QD78tgxKCWhkme8i30SAC1DF30HyP9/RC+LToOGKqSbkQ51+4qMEmSkLU DjFOxm1uc72Ax4+Y6qqs3/4eCjsShpf7tziJS9PnYjpdcokQBU2J6rbU1eLcNwVqAdAq U9KgPohLL76xebY6icOzWIfYeYfWonNlrFAaR3QbtYBYMzFi0fGw5KmCqv033nf0OO8u wPQ96rYlLGpTxCT5ljdQkDJ/nxBQ+xTT2ZrdusoIXaDKmvmIUp+0P32kLCcNeHaonc6w gBzEMpBa4zTmNczf9YKvpkAYHEOJShhuBXbj6cDc72W0cF3FydycO+U+MBPQPB4ofryv eZFg== X-Gm-Message-State: APjAAAUBw+OzFNdfCbFN69CXumnmK5SfKCtNjBQnYPQ+6awj6EWyDbak fizYkKQTZTM+0OUA3/kCaohhxpdnq5G7HP37LeY= X-Google-Smtp-Source: APXvYqzq8UPRrJfJ0wmsZswTCjUyrB8oZvG2T0FT+puktIIEMekl/zT+YUHyiboaJFuSOcFVFmY7pDdhRQkmBDOdfQE= X-Received: by 2002:ac2:5462:: with SMTP id e2mr19856735lfn.181.1574872780262; Wed, 27 Nov 2019 08:39:40 -0800 (PST) MIME-Version: 1.0 References: <20191126183451.GC29071@kernel.org> <87d0dexyij.fsf@toke.dk> <20191126190450.GD29071@kernel.org> <20191126221018.GA22719@kernel.org> <20191126221733.GB22719@kernel.org> <20191126231030.GE3145429@mini-arch.hsd1.ca.comcast.net> <20191126155228.0e6ed54c@cakuba.netronome.com> <20191127013901.GE29071@kernel.org> <20191127134553.GC22719@kernel.org> In-Reply-To: <20191127134553.GC22719@kernel.org> From: Alexei Starovoitov Date: Wed, 27 Nov 2019 08:39:28 -0800 Message-ID: Subject: Re: [PATCH] libbpf: Use PRIu64 for sym->st_value to fix build on 32-bit arches To: Arnaldo Carvalho de Melo Cc: Andrii Nakryiko , Jakub Kicinski , Stanislav Fomichev , =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , Andrii Nakryiko , Adrian Hunter , Alexei Starovoitov , Daniel Borkmann , Jiri Olsa , Martin KaFai Lau , Namhyung Kim , bpf , Networking , linux-perf-users@vger.kernel.org, Linux Kernel Mailing List , Quentin Monnet 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 Wed, Nov 27, 2019 at 5:45 AM Arnaldo Carvalho de Melo wrote: > > Another fix I'm carrying in my perf/core branch, Why in perf/core? I very much prefer all libbpf patches to go via normal route via bpf/net trees. We had enough conflicts in this merge window. Let's avoid them.