From: Yangtao Li <tiny.windzz@gmail.com>
To: tglx@linutronix.de, linux-kernel@vger.kernel.org
Cc: Yangtao Li <tiny.windzz@gmail.com>
Subject: [PATCH] clockchips: convert the code format to BIT()
Date: Wed, 16 Jan 2019 11:09:00 -0500 [thread overview]
Message-ID: <20190116160900.20771-1-tiny.windzz@gmail.com> (raw)
Use BIT() to do some clean-up.
Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
---
include/linux/clockchips.h | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h
index 8ae9a95ebf5b..39a2294e995b 100644
--- a/include/linux/clockchips.h
+++ b/include/linux/clockchips.h
@@ -43,9 +43,9 @@ enum clock_event_state {
/*
* Clock event features
*/
-# define CLOCK_EVT_FEAT_PERIODIC 0x000001
-# define CLOCK_EVT_FEAT_ONESHOT 0x000002
-# define CLOCK_EVT_FEAT_KTIME 0x000004
+# define CLOCK_EVT_FEAT_PERIODIC BIT(0)
+# define CLOCK_EVT_FEAT_ONESHOT BIT(1)
+# define CLOCK_EVT_FEAT_KTIME BIT(2)
/*
* x86(64) specific (mis)features:
@@ -53,19 +53,19 @@ enum clock_event_state {
* - Clockevent source stops in C3 State and needs broadcast support.
* - Local APIC timer is used as a dummy device.
*/
-# define CLOCK_EVT_FEAT_C3STOP 0x000008
-# define CLOCK_EVT_FEAT_DUMMY 0x000010
+# define CLOCK_EVT_FEAT_C3STOP BIT(3)
+# define CLOCK_EVT_FEAT_DUMMY BIT(4)
/*
* Core shall set the interrupt affinity dynamically in broadcast mode
*/
-# define CLOCK_EVT_FEAT_DYNIRQ 0x000020
-# define CLOCK_EVT_FEAT_PERCPU 0x000040
+# define CLOCK_EVT_FEAT_DYNIRQ BIT(5)
+# define CLOCK_EVT_FEAT_PERCPU BIT(6)
/*
* Clockevent device is based on a hrtimer for broadcast
*/
-# define CLOCK_EVT_FEAT_HRTIMER 0x000080
+# define CLOCK_EVT_FEAT_HRTIMER BIT(7)
/**
* struct clock_event_device - clock event device descriptor
--
2.17.0
next reply other threads:[~2019-01-16 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:09 Yangtao Li [this message]
2019-01-16 16:49 ` [PATCH] clockchips: convert the code format to BIT() Randy Dunlap
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=20190116160900.20771-1-tiny.windzz@gmail.com \
--to=tiny.windzz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).