From: Johan Hovold <johan@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Nicolas Schier <nicolas.schier@linux.dev>,
Masahiro Yamada <masahiroy@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH] modpost: drop '*_probe' from section check whitelist
Date: Tue, 16 Dec 2025 10:11:59 +0900 [thread overview]
Message-ID: <aUCx3948XuXmpWPo@hovoldconsulting.com> (raw)
In-Reply-To: <20251114041628.GA2566209@ax162>
Hi Nathan,
On Thu, Nov 13, 2025 at 09:16:28PM -0700, Nathan Chancellor wrote:
> On Wed, Nov 12, 2025 at 05:48:21PM +0100, Johan Hovold wrote:
> > Daniel has queued the clocksource fix for 6.19 now so I guess we can
> > just wait until both fixes hit mainline and either send this one to
> > Linus after that for -rc1 (or -rc2), or just wait until 6.20.
> >
> > I'll send a reminder when both are in Linus's tree.
>
> Thanks for the heads up! I think I would prefer having it bake in -next
> for a cycle so I will plan to apply it to kbuild-next once 6.19-rc1 is
> out. Then we should be able to catch any instances that crop up in new
> code from -next testing.
Both fixes are in rc1 so you should be able to apply this one now.
Johan
next prev parent reply other threads:[~2025-12-16 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 9:16 [PATCH] modpost: drop '*_probe' from section check whitelist Johan Hovold
2025-10-21 0:20 ` kernel test robot
2025-10-22 20:39 ` Nathan Chancellor
2025-11-12 16:48 ` Johan Hovold
2025-11-14 4:16 ` Nathan Chancellor
2025-11-14 8:45 ` Johan Hovold
2025-12-16 1:11 ` Johan Hovold [this message]
2025-11-15 15:36 ` Thomas Gleixner
2025-12-16 13:13 ` Nathan Chancellor
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 15:52 kernel test robot
2025-10-30 10:03 kernel test robot
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=aUCx3948XuXmpWPo@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=tglx@linutronix.de \
/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.