[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9PEtP7oLjRJTxFM@kroah.com>
Date: Fri, 27 Jan 2023 13:33:56 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Rob Herring <robh+dt@...nel.org>
Cc: linux-kernel@...r.kernel.org,
Michael Ellerman <mpe@...erman.id.au>,
Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Chen-Yu Tsai <wens@...e.org>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Samuel Holland <samuel@...lland.org>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Frank Rowand <frowand.list@...il.com>,
Liang He <windhl@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Thomas Zimmermann <tzimmermann@...e.de>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Douglas Anderson <dianders@...omium.org>,
Lyude Paul <lyude@...hat.com>,
Corentin Labbe <clabbe@...libre.com>,
Zou Wei <zou_wei@...wei.com>, linuxppc-dev@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 01/16] of: device: make of_device_uevent_modalias()
take a const device *
On Wed, Jan 11, 2023 at 08:54:04AM -0600, Rob Herring wrote:
> On Wed, Jan 11, 2023 at 5:30 AM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > of_device_uevent_modalias() does not modify the device pointer passed to
> > it, so mark it constant. In order to properly do this, a number of
> > busses need to have a modalias function added as they were attempting to
> > just point to of_device_uevent_modalias instead of their bus-specific
> > modalias function. This is fine except if the prototype for a bus and
> > device type modalias function diverges and then problems could happen. To
> > prevent all of that, just wrap the call to of_device_uevent_modalias()
> > directly for each bus and device type individually.
>
> Why not just put the wrapper function in the DT code instead of making
> 4 copies of it?
Ok, I looked at doing this today, but in the end, making "4" copies of
this is simpler overall. To do it your way would require a "const"
version of the function be added to the core, and then convert these 4
busses to use that, and then when the real function is converted to be
const, move all of these functions back over to use that again.
Lots of churn, and then in the end, we still have the mismatch of a
the same function callback being used in two different types of
callbacks (one a bus, one a class). This way we separate them to make
things much more obvious and self-contained.
So I'll keep this as-is for now, thanks.
greg k-h
Powered by blists - more mailing lists