linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ndesaulniers@google.com, natechancellor@gmail.com,
	ilia.lin@gmail.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] cpufreq: qcom-kryo: Fix section mismatch warning
Date: Thu, 20 Sep 2018 09:02:45 -0700	[thread overview]
Message-ID: <20180920160245.f4afwfyyz3nd4xvn@vireshk-mac-ubuntu> (raw)
In-Reply-To: <CAJZ5v0ipkaudrv7W5VP1_e9LERF6DLZuw+HtTf2Si4p=pbv9bw@mail.gmail.com>

On 20-09-18, 00:45, Rafael J. Wysocki wrote:
> Because __init things go away at one point and calling them from the
> other sections is a bad idea.  OTOH, __exit things are simply not
> needed in built-in drivers and they are never there if the driver is
> built-in, so calling them from the other sections is a bad idea too.

I assumed that the driver is calling platform_driver_probe() and so probe() can
be marked __init. But it doesn't do that to make deferred probing work.

-- 
viresh

  parent reply	other threads:[~2018-09-20 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 18:22 [PATCH v2] cpufreq: qcom-kryo: Fix section mismatch warning Nathan Chancellor
2018-09-19 21:32 ` Viresh Kumar
2018-09-19 21:45 ` Nick Desaulniers
2018-09-19 21:50   ` Viresh Kumar
2018-09-19 21:54     ` Viresh Kumar
2018-09-19 22:45       ` Rafael J. Wysocki
2018-09-19 22:48         ` Nathan Chancellor
2018-09-20 16:02         ` Viresh Kumar [this message]
2018-09-19 22:29   ` Nathan Chancellor

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=20180920160245.f4afwfyyz3nd4xvn@vireshk-mac-ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=ilia.lin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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;
as well as URLs for NNTP newsgroup(s).