From: <yanjiang.jin@windriver.com>
To: <tglx@linutronix.de>
Cc: <peterz@infradead.org>, <bigeasy@linutronix.de>,
<jinyanjiang@gmail.com>, <yanjiang.jin@windriver.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH] cpu.h: remove 3 obsolete macros
Date: Tue, 24 Oct 2017 14:23:41 +0800 [thread overview]
Message-ID: <20171024062341.179678-1-yanjiang.jin@windriver.com> (raw)
From: Yanjiang Jin <yanjiang.jin@windriver.com>
commit 530e9b76ae8f ("cpu/hotplug: Remove obsolete cpu hotplug
register/unregister functions")'
removes the below macros:
- #define CPU_UP_CANCELED 0x0004 /* CPU (unsigned)v NOT coming up */
- #define CPU_DOWN_PREPARE 0x0005 /* CPU (unsigned)v going down */
- #define CPU_DOWN_FAILED 0x0006 /* CPU (unsigned)v NOT going down */
But "CPU_UP_CANCELED_FROZEN, CPU_DOWN_PREPARE_FROZEN and
CPU_DOWN_FAILED_FROZEN" still refer to them, and nobody uses these "FROZEN"
macros now, we should remove them too.
Signed-off-by: Yanjiang Jin <yanjiang.jin@windriver.com>
---
include/linux/cpu.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/cpu.h b/include/linux/cpu.h
index ca73bc1..cd4771b 100644
--- a/include/linux/cpu.h
+++ b/include/linux/cpu.h
@@ -72,9 +72,6 @@ struct device *cpu_device_create(struct device *parent, void *drvdata,
#define CPU_ONLINE_FROZEN (CPU_ONLINE | CPU_TASKS_FROZEN)
#define CPU_UP_PREPARE_FROZEN (CPU_UP_PREPARE | CPU_TASKS_FROZEN)
-#define CPU_UP_CANCELED_FROZEN (CPU_UP_CANCELED | CPU_TASKS_FROZEN)
-#define CPU_DOWN_PREPARE_FROZEN (CPU_DOWN_PREPARE | CPU_TASKS_FROZEN)
-#define CPU_DOWN_FAILED_FROZEN (CPU_DOWN_FAILED | CPU_TASKS_FROZEN)
#define CPU_DEAD_FROZEN (CPU_DEAD | CPU_TASKS_FROZEN)
#ifdef CONFIG_SMP
--
1.9.1
next reply other threads:[~2017-10-24 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 6:23 yanjiang.jin [this message]
2017-10-24 8:48 ` [tip:smp/hotplug] cpu/hotplug: Remove obsolete notifier macros tip-bot for Yanjiang Jin
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=20171024062341.179678-1-yanjiang.jin@windriver.com \
--to=yanjiang.jin@windriver.com \
--cc=bigeasy@linutronix.de \
--cc=jinyanjiang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®