mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org
Subject: Re: [PATCH 16/27] score: create head files scatterlist.h scoreregs.h sections.h segment.h sembuf.h setup.h shmbuf.h shmparam.h sigcontext.h siginfo.h signal.h socket.h sockios.h statfs.h stat.h string.h swab.h syscalls.h system.h
Date: Tue, 9 Jun 2009 19:39:01 +0200	[thread overview]
Message-ID: <200906091939.01217.arnd@arndb.de> (raw)
In-Reply-To: <OF6E98041E.B5C6A199-ON482575D0.0023E412-482575D0.00245A53@sunplusct.com>

On Tuesday 09 June 2009, liqin.chen@sunplusct.com wrote:

> --- /dev/null
> +++ b/arch/score/include/asm/segment.h
> @@ -0,0 +1,21 @@
> +#ifndef _ASM_SCORE_SEGMENT_H
> +#define _ASM_SCORE_SEGMENT_H
> +
> +#ifndef __ASSEMBLY__
> +
> +typedef struct {
> +       unsigned long seg;
> +} mm_segment_t;
> +
> +#define KERNEL_DS      ((mm_segment_t){0})
> +#define USER_DS        KERNEL_DS
> +
> +# define get_ds()      (KERNEL_DS)
> +# define get_fs()      (current_thread_info()->addr_limit)
> +# define set_fs(x)     \
> +       do { current_thread_info()->addr_limit = (x); } while (0)
> +
> +# define segment_eq(a, b)      ((a).seg == (b).seg)
> +
> +# endif /* __ASSEMBLY__ */
> +#endif /* _ASM_SCORE_SEGMENT_H */

When I discussed these definitions with Michal Simek, we concluded
that they do not actually belong into segment.h. I added them to
asm-generic/uaccess.h, so if you can use that, you get them for free
and can have an empty segment.h file.

	Arnd <><

      reply	other threads:[~2009-06-09 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  6:32 liqin.chen
2009-06-09 17:39 ` Arnd Bergmann [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=200906091939.01217.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin.chen@sunplusct.com \
    --cc=torvalds@linux-foundation.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®