public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	"Ilya Leoshkevich" <iii@linux.ibm.com>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Philip Müller" <philm@manjaro.org>
Subject: Re: [PATCH stable 5.10 0/5] kbuild: Fix compilation for latest pahole release
Date: Wed, 19 Oct 2022 16:55:46 +0200	[thread overview]
Message-ID: <Y1AP8h6YGiDZAgyp@kroah.com> (raw)
In-Reply-To: <20221019085604.1017583-1-jolsa@kernel.org>

On Wed, Oct 19, 2022 at 10:55:59AM +0200, Jiri Olsa wrote:
> hi,
> new version of pahole (1.24) is causing compilation fail for 5.10
> stable kernel, discussed in here [1][2]. Sending fix for that plus
> dependency patches.
> 
> thanks,
> jirka
> 
> 
> [1] https://lore.kernel.org/bpf/20220825163538.vajnsv3xcpbhl47v@altlinux.org/
> [2] https://lore.kernel.org/bpf/YwQRKkmWqsf%2FDu6A@kernel.org/
> ---
> Andrii Nakryiko (1):
>       kbuild: skip per-CPU BTF generation for pahole v1.18-v1.21
> 
> Ilya Leoshkevich (1):
>       bpf: Generate BTF_KIND_FLOAT when linking vmlinux
> 
> Javier Martinez Canillas (1):
>       kbuild: Quote OBJCOPY var to avoid a pahole call break the build
> 
> Jiri Olsa (1):
>       kbuild: Unify options for BTF generation for vmlinux and modules
> 
> Martin Rodriguez Reboredo (1):
>       kbuild: Add skip_encoding_btf_enum64 option to pahole
> 
>  Makefile                |  3 +++
>  scripts/link-vmlinux.sh |  2 +-
>  scripts/pahole-flags.sh | 21 +++++++++++++++++++++
>  3 files changed, 25 insertions(+), 1 deletion(-)
>  create mode 100755 scripts/pahole-flags.sh

Ah, all showed up now.  I'll look at these tomorrow, thanks!

greg k-h

  parent reply	other threads:[~2022-10-19 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  8:55 [PATCH stable 5.10 0/5] kbuild: Fix compilation for latest pahole release Jiri Olsa
2022-10-19  8:56 ` [PATCH stable 5.10 1/5] bpf: Generate BTF_KIND_FLOAT when linking vmlinux Jiri Olsa
2022-10-19  8:56 ` [PATCH stable 5.10 2/5] kbuild: Quote OBJCOPY var to avoid a pahole call break the build Jiri Olsa
2022-10-19 10:28   ` Greg KH
2022-10-19 11:18     ` Jiri Olsa
2022-10-19  8:56 ` [PATCH stable 5.10 3/5] kbuild: skip per-CPU BTF generation for pahole v1.18-v1.21 Jiri Olsa
2022-10-19  8:56 ` [PATCH stable 5.10 4/5] kbuild: Unify options for BTF generation for vmlinux and modules Jiri Olsa
2022-10-19  8:56 ` [PATCH stable 5.10 5/5] kbuild: Add skip_encoding_btf_enum64 option to pahole Jiri Olsa
2022-10-19 14:55 ` Greg KH [this message]
2022-10-19 15:30   ` [PATCH stable 5.10 0/5] kbuild: Fix compilation for latest pahole release Jiri Olsa
2022-10-26 16:44 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y1AP8h6YGiDZAgyp@kroah.com \
    --to=greg@kroah.com \
    --cc=acme@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=iii@linux.ibm.com \
    --cc=javierm@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=nathan@kernel.org \
    --cc=philm@manjaro.org \
    --cc=stable@vger.kernel.org \
    --cc=yakoyoku@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox