From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>,
Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
Alan Maguire <alan.maguire@oracle.com>
Subject: Re: [PATCHv2 stable 6.1 0/2] btf, scripts: Update pahole options
Date: Thu, 18 Jan 2024 10:58:40 +0100 [thread overview]
Message-ID: <2024011832-unsoiled-sublime-9d16@gregkh> (raw)
In-Reply-To: <20240117133520.733288-1-jolsa@kernel.org>
On Wed, Jan 17, 2024 at 02:35:18PM +0100, Jiri Olsa wrote:
> hi,
> we need to be able to use latest pahole options for 6.1 kernels,
> updating the scripts/pahole-flags.sh with that (clean backports).
>
> thanks,
> jirka
>
> v2 changes:
> - added missing SOB
>
> ---
> Alan Maguire (1):
> bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25
>
> Martin Rodriguez Reboredo (1):
> btf, scripts: Exclude Rust CUs with pahole
>
> init/Kconfig | 2 +-
> lib/Kconfig.debug | 9 +++++++++
> scripts/pahole-flags.sh | 7 +++++++
> 3 files changed, 17 insertions(+), 1 deletion(-)
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-01-18 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:35 [PATCHv2 stable 6.1 0/2] btf, scripts: Update pahole options Jiri Olsa
2024-01-17 13:35 ` [PATCHv2 stable 6.1 1/2] btf, scripts: Exclude Rust CUs with pahole Jiri Olsa
2024-01-17 13:35 ` [PATCHv2 stable 6.1 2/2] bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25 Jiri Olsa
2024-01-18 9:58 ` 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=2024011832-unsoiled-sublime-9d16@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alan.maguire@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox