Skip to contentSkip to conversation

arm64: Define _TIF_POLLING_NRFLAG

PATCH New Mark Brown 3 participants 3 messages May 9, 2014 arm64

lore
Share & tools
lore

Mark Brown

author
#0 lore raw

PATCH 1/1 arm64: Define _TIF_POLLING_NRFLAG

From: Mark Brown <[email protected]>

arm64 defines TIF_POLLING_NRFLAG but not the corresponding shifted version, breaking the build with next-20140509 due to fd99f91aa007b (sched/idle:
Avoid spurious wakeup IPIs) which added a reference to the shifted version which is present on most arches.

---
 arch/arm64/include/asm/thread_info.h | 1 +
 1 file changed, 1 insertion(+)
arch/arm64/include/asm/thread_info.h +1 -0
index 720e70b66ffd..40ff87437734 100644
@@ -113,6 +113,7 @@ static inline struct thread_info *current_thread_info(void)
 #define _TIF_NEED_RESCHED	(1 << TIF_NEED_RESCHED)
 #define _TIF_NOTIFY_RESUME	(1 << TIF_NOTIFY_RESUME)
 #define _TIF_32BIT		(1 << TIF_32BIT)
+#define _TIF_POLLING_NRFLAG	(1 << TIF_POLLING_NRFLAG)
 
 #define _TIF_WORK_MASK		(_TIF_NEED_RESCHED | _TIF_SIGPENDING | \
 				 _TIF_NOTIFY_RESUME)
Signature · 1 line
2.0.0.rc2
#1 lore raw

PATCH 1/1 arm64: Define _TIF_POLLING_NRFLAG

Quoted 6 lines · Mark Brown

From: Mark Brown <[email protected]>

arm64 defines TIF_POLLING_NRFLAG but not the corresponding shifted version, breaking the build with next-20140509 due to fd99f91aa007b (sched/idle:
Avoid spurious wakeup IPIs) which added a reference to the shifted version which is present on most arches.

Sorry about that,

Should I get it in -tip so borkage and fix come in through the same tree, or what's the preferred routing?

maintainer
#2 lore raw

PATCH 1/1 arm64: Define _TIF_POLLING_NRFLAG

Quoted 11 lines · Peter Zijlstra
Quoted 6 lines · Mark Brown

From: Mark Brown <[email protected]>

arm64 defines TIF_POLLING_NRFLAG but not the corresponding shifted version, breaking the build with next-20140509 due to fd99f91aa007b (sched/idle:
Avoid spurious wakeup IPIs) which added a reference to the shifted version which is present on most arches.

Sorry about that,

I replied already in another thread. I don't think we need this bit at all.

Quoted 2 lines

Should I get it in -tip so borkage and fix come in through the same tree, or what's the preferred routing?

Whatever it's easier for you.

Signature · 1 line
Catalin