public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: asm/segment.h?
Date: Tue, 16 Aug 2005 14:42:47 -0700	[thread overview]
Message-ID: <43025DD7.3090007@vmware.com> (raw)
In-Reply-To: <83B69EC3-8677-4199-BDDB-375AE708234C@freescale.com>

Kumar Gala wrote:

> Looking at some architectures it appears that asm/uaccess.h should be  
> used instead of asm/segment.h.  Is this generally true that code in  
> segment.h should be moved into uaccess.h or is it still valid for an  
> architecture to have segment.h?


At least in i386, segment.h can be included by userspace programs, and 
although it really is the user include maintainers that should sort that 
out, moving segment.h into uaccess.h makes that job more tedious.

It looks like the proper thing to do for ppc is to deprecate segment.h 
entirely.

Zach

      reply	other threads:[~2005-08-16 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 21:28 asm/segment.h? Kumar Gala
2005-08-16 21:42 ` Zachary Amsden [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=43025DD7.3090007@vmware.com \
    --to=zach@vmware.com \
    --cc=kumar.gala@freescale.com \
    --cc=linux-kernel@vger.kernel.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