From: Feng Tang <feng.tang@intel.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] time: remove the unnecessary CONFIG_GENERIC_CLOCKEVENS check
Date: Fri, 6 Jan 2012 10:12:48 +0800 [thread overview]
Message-ID: <20120106021248.GA2691@feng-i7> (raw)
In-Reply-To: <1325762266.1807.9.camel@x61.thuisdomein>
Hi Paul,
On Thu, Jan 05, 2012 at 12:17:46PM +0100, Paul Bolle wrote:
> On Thu, 2012-01-05 at 21:28 +0800, Feng Tang wrote:
> > In kernel/time/Kconfig:
> > config GENERIC_CLOCKEVENTS_BUILD
> > bool
> > default y
> > depends on GENERIC_CLOCKEVENTS
> >
> > So there is no need to check CONFIG_GENERIC_CLOCKEVENTS if the
> > CONFIG_GENERIC_CLOCKEVENTS_BUILD is defined already.
>
> This is only true because nothing selects GENERIC_CLOCKEVENTS_BUILD
> directly, isn't it?
Thanks for pointing this out, your concern is valid, even though there
will be a warning message about the dependency corruption if the
GENERIC_CLOCKEVENTS_BUILD is directly selected while the
GENERIC_CLOCKEVENTS is N.
Thanks,
Feng
> So if we're being strict the patch explanation
> should mention that.
>
> (Maybe it's even better to simply state
> There is no need to check CONFIG_GENERIC_CLOCKEVENTS if
> CONFIG_GENERIC_CLOCKEVENTS_BUILD is defined.
>
> This prepares [...]
>
> as that would tell us just enough.)
>
> > This prepares for the total removal of GENERIC_CLOCKEVENTS_BUILD.
>
>
> Paul Bolle
next prev parent reply other threads:[~2012-01-06 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 13:28 [PATCH 1/2] time: remove the orphan option GENERIC_CLOCKEVENTS_MIGR Feng Tang
2012-01-05 13:28 ` [PATCH 2/2] time: remove the unnecessary CONFIG_GENERIC_CLOCKEVENS check Feng Tang
2012-01-05 11:17 ` Paul Bolle
2012-01-06 2:12 ` Feng Tang [this message]
2012-01-05 22:05 ` [PATCH 1/2] time: remove the orphan option GENERIC_CLOCKEVENTS_MIGR Paul Bolle
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=20120106021248.GA2691@feng-i7 \
--to=feng.tang@intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
/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