From: Greg Ungerer <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH] m68k: remove dead definition from thread-info.h
Date: Fri, 2 Sep 2011 22:48:45 +1000 [thread overview]
Message-ID: <4E60D0AD.905@snapgear.com> (raw)
In-Reply-To: <1314941497-32136-1-git-send-email-gerg@snapgear.com>
On 09/02/2011 03:31 PM, gerg@snapgear.com wrote:
> From: Greg Ungerer<gerg@uclinux.org>
>
> The conditional definition of the task_thread_info() macro based on
> ASM_OFFSETS_C being defined is not used. Remove it.
No, scratch this. From a clean build you need this
in place, before asm-offsets.h has been generated.
Regards
Greg
> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
> ---
> arch/m68k/include/asm/thread_info.h | 6 +-----
> 1 files changed, 1 insertions(+), 5 deletions(-)
>
> diff --git a/arch/m68k/include/asm/thread_info.h b/arch/m68k/include/asm/thread_info.h
> index e4e2159..6140b48 100644
> --- a/arch/m68k/include/asm/thread_info.h
> +++ b/arch/m68k/include/asm/thread_info.h
> @@ -53,13 +53,9 @@ struct thread_info {
> #include<asm/current.h>
> #endif
>
> -#ifdef ASM_OFFSETS_C
> -#define task_thread_info(tsk) ((struct thread_info *) NULL)
> -#else
> #include<asm/asm-offsets.h>
> -#define task_thread_info(tsk) ((struct thread_info *)((char *)tsk+TASK_INFO))
> -#endif
>
> +#define task_thread_info(tsk) ((struct thread_info *)((char *)tsk+TASK_INFO))
> #define init_thread_info (init_task.thread.info)
> #define task_stack_page(tsk) ((tsk)->stack)
> #define current_thread_info() task_thread_info(current)
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2011-09-02 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 5:31 [PATCH] m68k: remove dead definition from thread-info.h gerg
2011-09-02 12:48 ` Greg Ungerer [this message]
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=4E60D0AD.905@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
/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