From: Alexey Gladkov <legion@kernel.org>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Masahiro Yamada <masahiroy@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
linux-kbuild@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v6 9/9] s390: vmlinux.lds.S: Reorder sections
Date: Thu, 14 Aug 2025 23:51:40 +0200 [thread overview]
Message-ID: <aJ5abMK4nbdg4RBj@example.org> (raw)
In-Reply-To: <20250814141658.7684Fd6-hca@linux.ibm.com>
On Thu, Aug 14, 2025 at 04:16:58PM +0200, Heiko Carstens wrote:
> On Thu, Aug 14, 2025 at 03:07:17PM +0200, Alexey Gladkov wrote:
> > Reorder the sections to be placed in the default segment. The
> > .vmlinux.info use :NONE to override the default segment and tell the
> > linker to not put the section in any segment at all.
> >
> > >> s390x-linux-ld: .tmp_vmlinux1: warning: allocated section `.modinfo' not in segment
> > >> s390x-linux-ld: .tmp_vmlinux2: warning: allocated section `.modinfo' not in segment
> > >> s390x-linux-ld: vmlinux.unstripped: warning: allocated section `.modinfo' not in segment
> >
> > Cc: Heiko Carstens <hca@linux.ibm.com>
> > Cc: Vasily Gorbik <gor@linux.ibm.com>
> > Cc: Alexander Gordeev <agordeev@linux.ibm.com>
> > Cc: linux-s390@vger.kernel.org
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202506062053.zbkFBEnJ-lkp@intel.com/
> > Signed-off-by: Alexey Gladkov <legion@kernel.org>
> > Acked-by: Heiko Carstens <hca@linux.ibm.com>
> > ---
> > arch/s390/kernel/vmlinux.lds.S | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
>
> Is there any reason why you didn't reorder the patches?
> https://lore.kernel.org/all/aIeUq0qYXoNIePwd@example.org/
Oops! My bad. This patchset was added to linux-next and seems to be in
the correct order, but then it was removed and I seem to have lost this
change.
--
Rgrds, legion
prev parent reply other threads:[~2025-08-14 21:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:07 [PATCH v6 0/9] Add generated modalias to modules.builtin.modinfo Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 1/9] kbuild: always create intermediate vmlinux.unstripped Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 2/9] kbuild: keep .modinfo section in vmlinux.unstripped Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 3/9] kbuild: extract modules.builtin.modinfo from vmlinux.unstripped Alexey Gladkov
2025-08-17 12:34 ` Masahiro Yamada
2025-08-17 12:52 ` Alexey Gladkov
2025-08-18 6:43 ` Nathan Chancellor
2025-08-14 13:07 ` [PATCH v6 4/9] scsi: Always define blogic_pci_tbl structure Alexey Gladkov
2025-08-19 2:04 ` Martin K. Petersen
2025-08-19 7:18 ` Nathan Chancellor
2025-08-20 1:52 ` Martin K. Petersen
2025-08-20 16:11 ` Nathan Chancellor
2025-08-25 10:09 ` Alexey Gladkov
2025-08-25 16:56 ` Nathan Chancellor
2025-08-14 13:07 ` [PATCH v6 5/9] pinctrl: meson: Fix typo in device table macro Alexey Gladkov
2025-08-14 13:07 ` Alexey Gladkov
2025-08-18 9:11 ` Linus Walleij
2025-08-18 9:11 ` Linus Walleij
2025-08-14 13:07 ` [PATCH v6 6/9] modpost: Add modname to mod_device_table alias Alexey Gladkov
2025-08-14 13:26 ` Danilo Krummrich
2025-08-14 13:54 ` Alexey Gladkov
2025-08-14 14:03 ` Danilo Krummrich
2025-08-14 21:46 ` Alexey Gladkov
2025-08-14 22:17 ` Danilo Krummrich
2025-08-14 13:07 ` [PATCH v6 7/9] modpost: Create modalias for builtin modules Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 8/9] kbuild: vmlinux.unstripped should always depend on .vmlinux.export.o Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 9/9] s390: vmlinux.lds.S: Reorder sections Alexey Gladkov
2025-08-14 14:16 ` Heiko Carstens
2025-08-14 21:51 ` Alexey Gladkov [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=aJ5abMK4nbdg4RBj@example.org \
--to=legion@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=da.gomez@samsung.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.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.