linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Maulik Shah <quic_mkshah@quicinc.com>,
	bjorn.andersson@linaro.org, rafael@kernel.org,
	daniel.lezcano@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, ulf.hansson@linaro.org,
	quic_lsrao@quicinc.com, rnayak@codeaurora.org,
	Maulik Shah <quic_mkshah@quicinc.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 1/4] tick/sched: Export symbols used by cpuidle governors
Date: Wed, 01 Dec 2021 00:12:13 +0100	[thread overview]
Message-ID: <87wnkp9r1u.ffs@tglx> (raw)
In-Reply-To: <1637830481-21709-2-git-send-email-quic_mkshah@quicinc.com>

On Thu, Nov 25 2021 at 14:24, Maulik Shah wrote:
>  bool tick_nohz_enabled __read_mostly  = true;
> +EXPORT_SYMBOL(tick_nohz_enabled);

If any of this gets ever exported then with EXPORT_SYMBOL_GPL(), but I
agree with Rafael that there is no real value for this, so the exports
are not required either.

Thanks,

        tglx

  reply	other threads:[~2021-11-30 23:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25  8:54 [PATCH 0/4] Allow cpuidle governors to be compiled as modules Maulik Shah
2021-11-25  8:54 ` [PATCH 1/4] tick/sched: Export symbols used by cpuidle governors Maulik Shah
2021-11-30 23:12   ` Thomas Gleixner [this message]
2021-11-25  8:54 ` [PATCH 2/4] sched/core: " Maulik Shah
2021-11-25  9:35   ` Peter Zijlstra
2021-11-25 13:31     ` Maulik Shah
2021-11-26 16:34       ` Peter Zijlstra
2021-11-25  8:54 ` [PATCH 3/4] cpuidle: governor: export cpuidle governor functions Maulik Shah
2021-11-25  8:54 ` [PATCH 4/4] cpuidle: governors: Allow the governors to be compiled as modules Maulik Shah
2021-11-25 12:27 ` [PATCH 0/4] Allow cpuidle " Rafael J. Wysocki
2021-11-25 13:18   ` Maulik Shah
2021-11-25 15:46     ` Rafael J. Wysocki
2021-11-25 17:16 ` Doug Smythies

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=87wnkp9r1u.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=quic_lsrao@quicinc.com \
    --cc=quic_mkshah@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=rnayak@codeaurora.org \
    --cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).