All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: linux-riscv@lists.infradead.org, linux@armlinux.org.uk,
	catalin.marinas@arm.com, will@kernel.org, geert@linux-m68k.org,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	samitolvanen@google.com, alex@ghiti.fr, mcgrof@kernel.org,
	da.gomez@kernel.org, atomlin@atomlin.com,
	joe.lawrence@redhat.com, linux-arm-kernel@lists.infradead.org,
	linux-m68k@lists.linux-m68k.org, linux-modules@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] module: force sh_addr=0 for arch-specific sections
Date: Fri, 26 Jun 2026 08:21:19 +0000	[thread overview]
Message-ID: <178246207923.3816447.7091870447864059948.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260327080023.861105-1-petr.pavlu@suse.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Sami Tolvanen <samitolvanen@google.com>:

On Fri, 27 Mar 2026 08:58:59 +0100 you wrote:
> When linking modules with 'ld.bfd -r', sections defined without an address
> inherit the location counter, resulting in non-zero sh_addr values in the
> resulting .ko files. Relocatable objects are expected to have sh_addr=0 for
> all sections. Non-zero addresses are confusing in this context, typically
> worse compressible, and may cause tools to misbehave [1].
> 
> Joe Lawrence previously addressed the same issue in the main
> scripts/module.lds.S file [2] and we discussed that the same fix should be
> also applied to architecture-specific module sections. This series
> implements these changes.
> 
> [...]

Here is the summary with links:
  - [1/4] module, arm: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/ffe1545ce8a0
  - [2/4] module, arm64: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/c5553deb577f
  - [3/4] module, m68k: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/9cb4d4dc8227
  - [4/4] module, riscv: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/04e17ca3f77e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: linux-riscv@lists.infradead.org, linux@armlinux.org.uk,
	catalin.marinas@arm.com, will@kernel.org, geert@linux-m68k.org,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	samitolvanen@google.com, alex@ghiti.fr, mcgrof@kernel.org,
	da.gomez@kernel.org, atomlin@atomlin.com,
	joe.lawrence@redhat.com, linux-arm-kernel@lists.infradead.org,
	linux-m68k@lists.linux-m68k.org, linux-modules@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] module: force sh_addr=0 for arch-specific sections
Date: Fri, 26 Jun 2026 08:21:19 +0000	[thread overview]
Message-ID: <178246207923.3816447.7091870447864059948.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260327080023.861105-1-petr.pavlu@suse.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Sami Tolvanen <samitolvanen@google.com>:

On Fri, 27 Mar 2026 08:58:59 +0100 you wrote:
> When linking modules with 'ld.bfd -r', sections defined without an address
> inherit the location counter, resulting in non-zero sh_addr values in the
> resulting .ko files. Relocatable objects are expected to have sh_addr=0 for
> all sections. Non-zero addresses are confusing in this context, typically
> worse compressible, and may cause tools to misbehave [1].
> 
> Joe Lawrence previously addressed the same issue in the main
> scripts/module.lds.S file [2] and we discussed that the same fix should be
> also applied to architecture-specific module sections. This series
> implements these changes.
> 
> [...]

Here is the summary with links:
  - [1/4] module, arm: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/ffe1545ce8a0
  - [2/4] module, arm64: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/c5553deb577f
  - [3/4] module, m68k: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/9cb4d4dc8227
  - [4/4] module, riscv: force sh_addr=0 for arch-specific sections
    https://git.kernel.org/riscv/c/04e17ca3f77e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-06-26  8:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  7:58 [PATCH 0/4] module: force sh_addr=0 for arch-specific sections Petr Pavlu
2026-03-27  7:58 ` Petr Pavlu
2026-03-27  7:59 ` [PATCH 1/4] module, arm: " Petr Pavlu
2026-03-27  7:59   ` Petr Pavlu
2026-03-27  7:59 ` [PATCH 2/4] module, arm64: " Petr Pavlu
2026-03-27  7:59   ` Petr Pavlu
2026-03-27  7:59 ` [PATCH 3/4] module, m68k: " Petr Pavlu
2026-03-27  7:59   ` Petr Pavlu
2026-03-27  7:59 ` [PATCH 4/4] module, riscv: " Petr Pavlu
2026-03-27  7:59   ` Petr Pavlu
2026-05-26 23:40 ` [PATCH 0/4] module: " Sami Tolvanen
2026-05-26 23:40   ` Sami Tolvanen
2026-06-26  8:21 ` patchwork-bot+linux-riscv [this message]
2026-06-26  8:21   ` patchwork-bot+linux-riscv

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=178246207923.3816447.7091870447864059948.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=atomlin@atomlin.com \
    --cc=catalin.marinas@arm.com \
    --cc=da.gomez@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=joe.lawrence@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mcgrof@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=petr.pavlu@suse.com \
    --cc=pjw@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=will@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.