public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/qcom-irq-combiner: Rename driver structure
Date: Mon, 20 Oct 2025 11:18:16 +0200	[thread overview]
Message-ID: <aPX-WBsUUXXmpqdg@hovoldconsulting.com> (raw)
In-Reply-To: <87sefhzn18.ffs@tglx>

On Fri, Oct 17, 2025 at 03:16:19PM +0200, Thomas Gleixner wrote:
> On Fri, Oct 17 2025 at 07:52, Johan Hovold wrote:
> > The "_probe" suffix of the driver structure name prevents modpost from
> > warning about section mismatches so replace it to catch any future
> > issues like the recently fixed probe function being incorrectly marked
> > as __init.
> 
> I take this grudgingly, but not without pointing out again that this is
> just a horrible hack. Why can't this stuff be properly annotated and
> recorded in a throwaway section so that modpost can act on reliable data
> instead of using string matching on arbitrary function names?

This apparently dates back to 2006, but some of these magic patterns
were at least dropped a few years ago with commit e1dc1bfe5b27
("modpost: remove more symbol patterns from the section check
whitelist").

With the irqchip driver fixed and soon hopefully the stm clocksource
driver [1], we can retire also the special handling of the "_probe"
suffix. I've just sent a patch. [2]

Johan


[1] https://lore.kernel.org/lkml/20251017054943.7195-1-johan@kernel.org/
[2] https://lore.kernel.org/lkml/20251020091613.22562-1-johan@kernel.org/

  reply	other threads:[~2025-10-20  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  5:52 [PATCH] irqchip/qcom-irq-combiner: Rename driver structure Johan Hovold
2025-10-17 13:16 ` Thomas Gleixner
2025-10-20  9:18   ` Johan Hovold [this message]
2025-10-17 13:36 ` [tip: irq/drivers] " tip-bot2 for Johan Hovold

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=aPX-WBsUUXXmpqdg@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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