From: Paul Mackerras <paulus@samba.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, <hch@infradead.org>,
<davem@davemloft.net>,
"Gala Kumar K.-galak" <galak@freescale.com>, <akpm@osdl.org>,
<linux-kernel@vger.kernel.org>, <linuxppc-dev@ozlabs.org>,
<zach@vmware.com>
Subject: Re: [PATCH] ppc32: removed usage of <asm/segment.h>
Date: Fri, 19 Aug 2005 09:40:27 +1000 [thread overview]
Message-ID: <17157.7275.960362.923238@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <A4C8B92D-B390-4BF8-A6D5-106ACBD0E716@freescale.com>
Kumar Gala writes:
> So after all of this its not clear to me if its acceptable to kill
> all users of <asm/segment.h> in the kernel and to move code that
> exists in <asm/segment.h> to <asm/uaccess.h> for arch's that need it.
<asm/segment.h> doesn't describe any part of the user/kernel ABI, so
we should be OK to kill it. I would say we should remove the ppc and
ppc64 versions of it once 2.6.13 is out, and offer the other arch
maintainers a patch that moves their stuff as you suggest. I think
also we could submit patches to remove the places where it is included
in generic kernel code post 2.6.13.
Paul.
prev parent reply other threads:[~2005-08-18 23:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:00 Kumar Gala
2005-08-17 1:38 ` Paul Mackerras
2005-08-17 3:33 ` David S. Miller
2005-08-17 5:43 ` Kumar Gala
2005-08-17 8:16 ` Geert Uytterhoeven
2005-08-17 8:30 ` Christoph Hellwig
2005-08-17 8:56 ` Miklos Szeredi
2005-08-17 9:09 ` Christoph Hellwig
2005-08-17 9:15 ` Miklos Szeredi
2005-08-17 9:20 ` Christoph Hellwig
2005-08-17 10:07 ` Miklos Szeredi
2005-08-18 16:25 ` Kumar Gala
2005-08-18 23:40 ` Paul Mackerras [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=17157.7275.960362.923238@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=galak@freescale.com \
--cc=hch@infradead.org \
--cc=kumar.gala@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miklos@szeredi.hu \
--cc=zach@vmware.com \
/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®