public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Johan Hovold <johan@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: Thu, 13 Nov 2025 21:16:28 -0700	[thread overview]
Message-ID: <20251114041628.GA2566209@ax162> (raw)
In-Reply-To: <aRS6VQCKB7dXGbXx@hovoldconsulting.com>

Hi Johan,

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.

Cheers,
Nathan

  reply	other threads:[~2025-11-14  4:16 UTC|newest]

Thread overview: 9+ 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 [this message]
2025-11-14  8:45       ` Johan Hovold
2025-12-16  1:11       ` Johan Hovold
2025-11-15 15:36 ` Thomas Gleixner
2025-12-16 13:13 ` Nathan Chancellor

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=20251114041628.GA2566209@ax162 \
    --to=nathan@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox