mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Tim Abbott <tabbott@ksplice.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 1/2] m68k: Make thread_info.h usable from assembly.
Date: Sun, 27 Sep 2009 11:55:55 +0200	[thread overview]
Message-ID: <10f740e80909270255y18c2840bh14c6a4ddfdb0a916@mail.gmail.com> (raw)
In-Reply-To: <1253119466-19488-2-git-send-email-tabbott@ksplice.com>

On Wed, Sep 16, 2009 at 18:44, Tim Abbott <tabbott@ksplice.com> wrote:
> Signed-off-by: Tim Abbott <tabbott@ksplice.com>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Roman Zippel <zippel@linux-m68k.org>
> Cc: linux-m68k@lists.linux-m68k.org
> Cc: Sam Ravnborg <sam@ravnborg.org>
> ---
>  arch/m68k/include/asm/thread_info_mm.h |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/m68k/include/asm/thread_info_mm.h b/arch/m68k/include/asm/thread_info_mm.h
> index b6da388..5f36cf1 100644
> --- a/arch/m68k/include/asm/thread_info_mm.h
> +++ b/arch/m68k/include/asm/thread_info_mm.h
> @@ -8,6 +8,7 @@
>  #include <asm/types.h>
>  #include <asm/page.h>
>
> +#ifndef __ASSEMBLY__
>  struct thread_info {
>        struct task_struct      *task;          /* main task structure */
>        unsigned long           flags;
> @@ -16,6 +17,7 @@ struct thread_info {
>        __u32 cpu; /* should always be 0 on m68k */
>        struct restart_block    restart_block;
>  };
> +#endif /* __ASSEMBLY__ */
>
>  #define PREEMPT_ACTIVE         0x4000000

This is not sufficient. <asm/thread_info_mm.h> pulls in <asm/current.h>,
which contains C only. So you also need:

--- a/arch/m68k/include/asm/thread_info_mm.h
+++ b/arch/m68k/include/asm/thread_info_mm.h
@@ -4,11 +4,12 @@
 #ifndef ASM_OFFSETS_C
 #include <asm/asm-offsets.h>
 #endif
-#include <asm/current.h>
 #include <asm/types.h>
 #include <asm/page.h>

 #ifndef __ASSEMBLY__
+#include <asm/current.h>
+
 struct thread_info {
 	struct task_struct	*task;		/* main task structure */
 	unsigned long		flags;


Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2009-09-27  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:44 [PATCH v2 0/2] Linker script cleanup patches for m68k Tim Abbott
2009-09-16 16:44 ` [PATCH v2 1/2] m68k: Make thread_info.h usable from assembly Tim Abbott
2009-09-27  9:55   ` Geert Uytterhoeven [this message]
2009-09-27 11:58     ` Sam Ravnborg
2009-11-20  7:56       ` Geert Uytterhoeven
2009-09-16 16:44 ` [PATCH v2 2/2] m68k: Cleanup linker scripts using new linker script macros Tim Abbott
2009-09-27  9:58   ` Geert Uytterhoeven
2009-09-27 13:01     ` Andreas Schwab
2009-09-27 17:57       ` Tim Abbott
2009-09-29 17:12         ` Andreas Schwab
2009-09-30  6:53           ` Sam Ravnborg
2009-10-04  8:32             ` Geert Uytterhoeven

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=10f740e80909270255y18c2840bh14c6a4ddfdb0a916@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tabbott@ksplice.com \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®