All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dan Kegel <dank@kegel.com>, Roman Zippel <zippel@linux-m68k.org>,
	Matthias Urlichs <smurf@smurf.noris.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Getting kernel.org kernel to build for m68k?
Date: Sun, 5 Sep 2004 12:03:25 +0100	[thread overview]
Message-ID: <20040905120325.A29363@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0409051224020.30282@anakin>; from geert@linux-m68k.org on Sun, Sep 05, 2004 at 12:41:08PM +0200

> Hence if no one objects, I'll submit the patch to Andrew and Linus.

the common code changes below are not okay.  Please fir m68k into one of
the schemes we have for thread_info/task_struct already.


> --- linux-2.6.8.1/include/linux/sched.h	2004-08-04 12:14:38.000000000 +0200
> +++ linux-m68k-2.6.8.1/include/linux/sched.h	2004-09-04 21:18:59.000000000 +0200
> @@ -977,6 +977,7 @@ static inline struct mm_struct * get_tas
>  	return mm;
>  }
> 
> +#ifndef __HAVE_THREAD_FUNCTIONS
> 
>  /* set thread flags in other task's structures
>   * - see asm/thread_info.h for TIF_xxxx flags available
> @@ -1006,6 +1007,8 @@ static inline int test_tsk_thread_flag(s
>  	return test_ti_thread_flag(tsk->thread_info,flag);
>  }
> 
> +#endif	/* __HAVE_THREAD_FUNCTIONS */
> +
>  static inline void set_tsk_need_resched(struct task_struct *tsk)
>  {
>  	set_tsk_thread_flag(tsk,TIF_NEED_RESCHED);
> --- linux-2.6.8.1/include/linux/thread_info.h	2004-04-27 20:42:22.000000000 +0200
> +++ linux-m68k-2.6.8.1/include/linux/thread_info.h	2004-09-04 21:24:36.000000000 +0200
> @@ -21,6 +21,7 @@ extern long do_no_restart_syscall(struct
>  #include <asm/thread_info.h>
> 
>  #ifdef __KERNEL__
> +#ifndef __HAVE_THREAD_FUNCTIONS
> 
>  /*
>   * flag set/clear/test wrappers
> @@ -77,16 +78,11 @@ static inline int test_ti_thread_flag(st
>  	return test_bit(flag,&ti->flags);
>  }
> 
> -static inline void set_need_resched(void)
> -{
> -	set_thread_flag(TIF_NEED_RESCHED);
> -}
> +#endif	/* __HAVE_THREAD_FUNCTIONS */
> 
> -static inline void clear_need_resched(void)
> -{
> -	clear_thread_flag(TIF_NEED_RESCHED);
> -}
> +#define set_need_resched() set_thread_flag(TIF_NEED_RESCHED)
> +#define clear_need_resched(void) clear_thread_flag(TIF_NEED_RESCHED)
> 
> -#endif
> +#endif	/* __KERNEL__ */
> 
>  #endif /* _LINUX_THREAD_INFO_H */
> 
> Gr{oetje,eeting}s,
> 
> 						Geert
> 
> [*] For reference:
> 
>     http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-2.6.x-merging/POSTPONED/156-thread_info.diff
> 
> --
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
---end quoted text---

  parent reply	other threads:[~2004-09-05 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  5:35 Getting kernel.org kernel to build for m68k? Dan Kegel
2004-09-01  8:36 ` Geert Uytterhoeven
2004-09-05 10:41   ` Geert Uytterhoeven
2004-09-05 11:01     ` Matthias Urlichs
2004-09-05 11:03     ` Christoph Hellwig [this message]
2004-09-05 13:19       ` Matthias Urlichs
2004-09-05 13:49         ` Christoph Hellwig
2004-09-05 15:45           ` Roman Zippel
2004-09-05 15:48           ` Matthias Urlichs

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=20040905120325.A29363@infradead.org \
    --to=hch@infradead.org \
    --cc=dank@kegel.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=smurf@smurf.noris.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.