From: Greg KH <gregkh@linuxfoundation.org>
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>
Subject: Re: [PATCH stable 5.15 0/2] kbuild: Fix compilation for latest pahole release
Date: Sun, 4 Sep 2022 16:10:09 +0200 [thread overview]
Message-ID: <YxSxwZWkYMmtcsmA@kroah.com> (raw)
In-Reply-To: <20220904131901.13025-1-jolsa@kernel.org>
On Sun, Sep 04, 2022 at 03:18:59PM +0200, Jiri Olsa wrote:
> hi,
> new version of pahole (1.24) is causing compilation fail for 5.15
> stable kernel, discussed in here [1][2]. Sending fix for that plus
> one dependency patch.
>
> Note for patch 1:
> there was one extra line change in scripts/pahole-flags.sh file in
> its linux tree merge commit:
>
> fc02cb2b37fe Merge tag 'net-next-for-5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
>
> not sure how/if to track that, I squashed the change in.
Squashing is fine, thanks.
And do we also need this for kernels older than 5.15? Like 5.10 and 5.4?
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-04 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 13:18 [PATCH stable 5.15 0/2] kbuild: Fix compilation for latest pahole release Jiri Olsa
2022-09-04 13:19 ` [PATCH stable 5.15 1/2] kbuild: Unify options for BTF generation for vmlinux and modules Jiri Olsa
2022-09-04 13:19 ` [PATCH stable 5.15 2/2] kbuild: Add skip_encoding_btf_enum64 option to pahole Jiri Olsa
2022-09-04 13:20 ` kernel test robot
2022-09-04 14:09 ` Greg KH
2022-09-04 14:09 ` Greg KH
2022-09-04 14:10 ` Greg KH [this message]
2022-09-05 7:04 ` [PATCH stable 5.15 0/2] kbuild: Fix compilation for latest pahole release Jiri Olsa
2022-09-06 12:03 ` Greg KH
2022-09-18 22:14 ` Jiri Olsa
2022-10-17 18:02 ` Nathan Chancellor
2022-10-17 21:27 ` Jiri Olsa
2022-10-18 6:45 ` 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=YxSxwZWkYMmtcsmA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.