public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH 0/3] kbuild: remove PROVIDE() and refactor vmlinux_link steps
Date: Tue, 28 May 2024 11:42:37 +0200	[thread overview]
Message-ID: <ZlWnDT1S7n4XrAb5@krava> (raw)
In-Reply-To: <20240522114755.318238-1-masahiroy@kernel.org>

On Wed, May 22, 2024 at 08:47:52PM +0900, Masahiro Yamada wrote:
> 
>  - Remove PROVIDE() in the linker script
>  - Merge temporary vmlinux link steps for BTF and kallsyms
> 
> 
> 
> Masahiro Yamada (3):
>   kbuild: refactor variables in scripts/link-vmlinux.sh
>   kbuild: remove PROVIDE() for kallsyms symbols
>   kbuild: merge temp vmlinux for CONFIG_DEBUG_INFO_BTF and
>     CONFIG_KALLSYMS

lgtm, fyi I ran bpf CI on top of this change and passed

https://github.com/kernel-patches/bpf/pull/7104

jirka

> 
>  include/asm-generic/vmlinux.lds.h | 19 -------
>  kernel/kallsyms_internal.h        |  5 --
>  scripts/kallsyms.c                |  6 ---
>  scripts/link-vmlinux.sh           | 87 ++++++++++++++++---------------
>  4 files changed, 45 insertions(+), 72 deletions(-)
> 
> -- 
> 2.40.1
> 
> 

      parent reply	other threads:[~2024-05-28  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 11:47 [PATCH 0/3] kbuild: remove PROVIDE() and refactor vmlinux_link steps Masahiro Yamada
2024-05-22 11:47 ` [PATCH 2/3] kbuild: remove PROVIDE() for kallsyms symbols Masahiro Yamada
2024-05-23  9:31   ` Ard Biesheuvel
2024-05-25 16:43     ` Masahiro Yamada
2024-05-28  9:42 ` Jiri Olsa [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=ZlWnDT1S7n4XrAb5@krava \
    --to=olsajiri@gmail.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bpf@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    /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