From: Ronald Warsow <rwarsow@gmx.de>
To: Thomas Backlund <tmb@tmb.nu>, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.18 000/181] 5.18.8-rc1 review
Date: Tue, 28 Jun 2022 23:20:30 +0200 [thread overview]
Message-ID: <d54fe0fa-fa02-cc27-d523-938f8c5edd9c@gmx.de> (raw)
In-Reply-To: <f0cdac2a-79f3-af1c-eac9-698b0c8196a3@tmb.nu>
On 28.06.22 22:18, Thomas Backlund wrote:
> Den 2022-06-27 kl. 19:38, skrev Ronald Warsow:
>> hallo Greg
>>
>> 5.18.8-rc1
>>
>> compiles (see [1]), boots and runs here on x86_64
>> (Intel i5-11400, Fedora 36)
>>
>> [1]
>> a regression against 5.18.7:
>>
>> ...
>>
>> LD vmlinux.o
>> MODPOST vmlinux.symvers
>> WARNING: modpost: vmlinux.o(___ksymtab_gpl+tick_nohz_full_setup+0x0):
>> Section mismatch in reference from the variable
>> __ksymtab_tick_nohz_full_setup to the function
>> .init.text:tick_nohz_full_setup()
>> The symbol tick_nohz_full_setup is exported and annotated __init
>> Fix this by removing the __init annotation of tick_nohz_full_setup or
>> drop the export.
>
>
> Should be fixed by:
>
>
> From 2390095113e98fc52fffe35c5206d30d9efe3f78 Mon Sep 17 00:00:00 2001
> From: Masahiro Yamada <masahiroy@kernel.org>
> Date: Mon, 27 Jun 2022 12:22:09 +0900
> Subject: [PATCH] tick/nohz: unexport __init-annotated tick_nohz_full_setup()
>
> --
> Thomas
>
Thanks Thomas
--
Ronald
next prev parent reply other threads:[~2022-06-28 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 20:18 [PATCH 5.18 000/181] 5.18.8-rc1 review Thomas Backlund
2022-06-28 21:20 ` Ronald Warsow [this message]
2022-06-30 9:21 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-06-27 16:38 Ronald Warsow
2022-06-27 11:19 Greg Kroah-Hartman
2022-06-27 17:49 ` Florian Fainelli
2022-06-27 18:08 ` Daniel Díaz
2022-06-27 21:44 ` Rudi Heitbaum
2022-06-27 21:50 ` Shuah Khan
2022-06-27 21:52 ` Ron Economos
2022-06-27 23:42 ` Guenter Roeck
2022-06-28 2:49 ` Justin Forbes
2022-06-28 6:28 ` Bagas Sanjaya
2022-06-28 13:23 ` Sudip Mukherjee
2022-07-06 7:41 ` Bagas Sanjaya
2022-07-06 23:51 ` Shuah Khan
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=d54fe0fa-fa02-cc27-d523-938f8c5edd9c@gmx.de \
--to=rwarsow@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tmb@tmb.nu \
/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;
as well as URLs for NNTP newsgroup(s).