From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Vishal Mahaveer <vishalm@ti.com>,
Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PM: QoS: Export dev_pm_qos_read_value
Date: Thu, 3 Oct 2024 08:49:48 +0200 [thread overview]
Message-ID: <2024100336-left-shadily-3321@gregkh> (raw)
In-Reply-To: <tqsrnsvciupbovlalqsnrp5whst2mrpqntjblvymcunpesvake@o3gxa7vik7he>
On Thu, Oct 03, 2024 at 08:28:12AM +0200, Markus Schneider-Pargmann wrote:
> On Thu, Oct 03, 2024 at 08:02:04AM GMT, Greg Kroah-Hartman wrote:
> > On Wed, Oct 02, 2024 at 09:44:46PM +0200, Markus Schneider-Pargmann wrote:
> > > Export the function dev_pm_qos_read_value(). Most other functions
> > > mentioned in Documentation/power/pm_qos_interface.rst are already
> > > exported, so export this one as well.
> > >
> > > This function will be used to read the resume latency in a driver that
> > > can also be compiled as a module.
> >
> > We don't add exports for no in-kernel users, sorry. Send this as part
> > of a series that requires it.
>
> Sorry if this was unclear, it is for an in-kernel driver (ti_sci.c) that
> can be built as a module. When built as a module it can't use this
> function if it is not exported.
So the current kernel build is broken? If so, please add a "Fixes:" tag
and say this in the changelog.
If not, again, just make it part of the series where it is needed.
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-03 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 19:44 [PATCH v2] PM: QoS: Export dev_pm_qos_read_value Markus Schneider-Pargmann
2024-10-03 6:02 ` Greg Kroah-Hartman
2024-10-03 6:28 ` Markus Schneider-Pargmann
2024-10-03 6:49 ` Greg Kroah-Hartman [this message]
2024-10-03 7:21 ` Markus Schneider-Pargmann
2024-10-25 13:15 ` Nishanth Menon
2024-10-25 14:50 ` Rafael J. Wysocki
2024-10-25 15:16 ` Nishanth Menon
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=2024100336-left-shadily-3321@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=d-gole@ti.com \
--cc=khilman@baylibre.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=vishalm@ti.com \
/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