[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563db91f-3080-4a45-ba0d-04f415ed90d9@oss.qualcomm.com>
Date: Mon, 30 Jun 2025 19:25:55 +0200
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>,
Agustin Vega-Frias <agustinv@...eaurora.org>,
Marc Zyngier <maz@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
Jeff Hugo <jeff.hugo@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
Markus Schneider-Pargmann <msp@...libre.com>
Subject: Re: [PATCH] irqchip/qcom-irq-combiner: Rename driver struct to end in
_driver
On 30-Jun-25 19:23, Uwe Kleine-König wrote:
> The modpost section mismatch checks are more lax for objects that have a
> name that ends in "_probe". This is not justified here though, so rename
> the driver struct according to the usual naming choice.
>
> Note that this change indeed results in modpost identifying a section
> mismatch in this driver. This is not a false positive and should be
> fixed by either converting the driver to use platform_driver_probe() or
> by dropping __init from the .probe() callback. This problem was
> introduced in commit f20cc9b00c7b ("irqchip/qcom: Add IRQ combiner
> driver").
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...libre.com>
> ---
> Hello,
>
> I don't know if platform_driver_probe() works here, it might happen that
> the driver is probed before the matching device appears. As I don't have
> a machine with such a device I won't create a patch fixing the issue,
> but if you have questions don't hesitate to ask.
>
> Please consider this patch as a bug report and better only apply it when
> the issue is addressed to not result in build regressions.
+Jeff is probably the last person on Earth that officially has one
Konrad
Powered by blists - more mailing lists