From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH] task_stack.h: remove obsolete __HAVE_ARCH_KSTACK_END check
Date: Thu, 03 Apr 2025 14:33:03 +0200 [thread overview]
Message-ID: <20250403-kstack-end-v1-1-7798e71f34d1@linaro.org> (raw)
From: Pasha Tatashin <pasha.tatashin@soleen.com>
Remove __HAVE_ARCH_KSTACK_END as it has been osolete since removal of
metag architecture in v4.17.
Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Link: https://lore.kernel.org/20240311164638.2015063-2-pasha.tatashin@soleen.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Resending Pashas cleanup patch as it fell off the planet
a year ago because it was part of a patch series that
did not go anywhere at the time.
Andrew maybe you can pick this one up?
---
include/linux/sched/task_stack.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/sched/task_stack.h b/include/linux/sched/task_stack.h
index cffad65bdc6a970084cbcfea1913ba53a12dbb4f..85c5a6392e02776e462b2b76e8e1aeb9e1f91af0 100644
--- a/include/linux/sched/task_stack.h
+++ b/include/linux/sched/task_stack.h
@@ -106,7 +106,6 @@ static inline unsigned long stack_not_used(struct task_struct *p)
#endif
extern void set_task_stack_end_magic(struct task_struct *tsk);
-#ifndef __HAVE_ARCH_KSTACK_END
static inline int kstack_end(void *addr)
{
/* Reliable end of stack detection:
@@ -114,6 +113,5 @@ static inline int kstack_end(void *addr)
*/
return !(((unsigned long)addr+sizeof(void*)-1) & (THREAD_SIZE-sizeof(void*)));
}
-#endif
#endif /* _LINUX_SCHED_TASK_STACK_H */
---
base-commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557
change-id: 20250403-kstack-end-9813410f860d
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
reply other threads:[~2025-04-03 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250403-kstack-end-v1-1-7798e71f34d1@linaro.org \
--to=linus.walleij@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
/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®