From: Greg KH <gregkh@linuxfoundation.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: stable <stable@vger.kernel.org>,
Andres Freund <andres@anarazel.de>,
Quentin Monnet <quentin@isovalent.com>,
bpf@vger.kernel.org, Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: stable backport of patches fixing perf, libbpf and bpftools compilation with binutils 2.40
Date: Wed, 15 Mar 2023 09:43:46 +0100 [thread overview]
Message-ID: <ZBGFQvnRspELWT6x@kroah.com> (raw)
In-Reply-To: <e6e2df31-6327-f2ad-3049-0cbfa214ae5c@hauke-m.de>
On Mon, Mar 06, 2023 at 11:58:12PM +0100, Hauke Mehrtens wrote:
> Hi,
>
> The following patches are fixing the compilation of perf, bpf_jit_disasm and
> bpftools with binutils 2.40.
>
> commit cfd59ca91467056bb2c36907b2fa67b8e1af9952
> Subject: tools build: Add feature test for init_disassemble_info API changes
>
> commit a45b3d6926231c3d024ea0de4f7bd967f83709ee
> Subject: tools include: add dis-asm-compat.h to handle version differences
>
> commit 83aa0120487e8bc3f231e72c460add783f71f17c
> Subject: tools perf: Fix compilation error with new binutils
>
> commit 96ed066054abf11c7d3e106e3011a51f3f1227a3
> Subject: tools bpf_jit_disasm: Fix compilation error with new binutils
>
> commit 600b7b26c07a070d0153daa76b3806c1e52c9e00
> Subject: tools bpftool: Fix compilation error with new binutils
>
>
> Please backport these patches to kernel 5.15. Backporting them to 5.10
> resulted in more merge conflicts for me so I did not continue if it.
Now all queued up to 5.15, thanks.
greg k-h
prev parent reply other threads:[~2023-03-15 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 22:58 stable backport of patches fixing perf, libbpf and bpftools compilation with binutils 2.40 Hauke Mehrtens
2023-03-15 8:43 ` Greg KH [this message]
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=ZBGFQvnRspELWT6x@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=andres@anarazel.de \
--cc=bpf@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=quentin@isovalent.com \
--cc=stable@vger.kernel.org \
/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.