mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH v2 1/1] PM: Revert "Add EXPORT macros for exporting PM functions"
Date: Thu, 16 Jan 2025 16:55:05 +0000	[thread overview]
Message-ID: <9f0c1792-a569-41c0-9e90-e52717185359@opensource.cirrus.com> (raw)
In-Reply-To: <CAJZ5v0izBnSGjmjO7T+_gEhrSib0==_bRXnsLEdzEjbH0cZDqg@mail.gmail.com>

On 16/01/2025 4:09 pm, Rafael J. Wysocki wrote:
> On Thu, Jan 16, 2025 at 4:44 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>>
>> The introduced macros are not doing what they intend for, namely
>> they won't eliminate the code when CONFIG_PM=n.
> 
> I don't think they have ever been expected to eliminate the code then.
> They just don't export the symbols in that case.
> 
>> Also there were no users of them for all this time.
>

I had code changes to use them but they got lost at the bottom of a long
backlog of other commits and have never been upstreamed. Removing these
macros is fine with me.

(apologies if you get this msg twice, there was a problem with email)

> This actually is a good argument for dropping stuff.
> 
>> Drop them for good and to avoid possible misleading.
>>
>> This reverts commit 41a337b40e983db4f0e1602308109f2b93687a06.
>>
>> Reported-by: Adrian Hunter <adrian.hunter@intel.com>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>> v2: elaborated commit message (Greg), Cc'ed to the original author
>>   include/linux/pm.h | 4 ----
>>   1 file changed, 4 deletions(-)
>>
>> diff --git a/include/linux/pm.h b/include/linux/pm.h
>> index 08c37b83fea8..5dae93817141 100644
>> --- a/include/linux/pm.h
>> +++ b/include/linux/pm.h
>> @@ -384,12 +384,8 @@ const struct dev_pm_ops name = { \
>>
>>   #ifdef CONFIG_PM
>>   #define _EXPORT_DEV_PM_OPS(name, license, ns)          _EXPORT_PM_OPS(name, license, ns)
>> -#define EXPORT_PM_FN_GPL(name)                         EXPORT_SYMBOL_GPL(name)
>> -#define EXPORT_PM_FN_NS_GPL(name, ns)                  EXPORT_SYMBOL_NS_GPL(name, "ns")
>>   #else
>>   #define _EXPORT_DEV_PM_OPS(name, license, ns)          _DISCARD_PM_OPS(name, license, ns)
>> -#define EXPORT_PM_FN_GPL(name)
>> -#define EXPORT_PM_FN_NS_GPL(name, ns)
>>   #endif
>>
>>   #ifdef CONFIG_PM_SLEEP
>> --


  parent reply	other threads:[~2025-01-16 16:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 15:43 Andy Shevchenko
2025-01-16 16:09 ` Rafael J. Wysocki
2025-01-16 16:13   ` Andy Shevchenko
2025-01-16 16:27     ` Rafael J. Wysocki
2025-01-16 16:33       ` Andy Shevchenko
2025-01-16 19:18         ` Rafael J. Wysocki
2025-01-17 13:39           ` Andy Shevchenko
2025-01-23 20:23             ` Rafael J. Wysocki
2025-01-16 16:55   ` Richard Fitzgerald [this message]
2025-01-17 13:40     ` Andy Shevchenko

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=9f0c1792-a569-41c0-9e90-e52717185359@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=adrian.hunter@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    /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

all inboxes | Powered by JetHome®