From: Jon Loeliger <jdl@freescale•com>
To: linuxppc-dev@ozlabs•org, linuxppc64-dev@ozlabs•org
Subject: Re: PATCH powerpc Merge asm-ppc*/seccomp.h
Date: Fri, 23 Sep 2005 07:54:52 -0500 [thread overview]
Message-ID: <E1EIn4m-0001po-Bx@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 23 Sep 2005 11:08:09 +0200." <20050923090809.GA31688@lst.de>
So, like, the other day Christoph Hellwig mumbled:
> >
> > But keep the #include? It's actually the part
> > that is defining TIF_32BIT for ppc64 (indirectly
> > through linux/thread_info.h and asm/thread_info.h).
> > Won't those bits be needed still?
>
> I'm not sure. This header definitly doesn't need it, but I suspect
> seccompt.c expects to get it via this header.
I dug around in this a bit. The nested includes here yield
a fairly wide distribution of availability of TIF_32BIT.
I'm hesitant to remove it in this "merge" patch, so I
will leave its removal to a follow on patch/effort.
New patch with #if test removed coming up.
jdl
prev parent reply other threads:[~2005-09-23 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 18:20 PATCH powerpc Merge asm-ppc*/seccomp.h Jon Loeliger
2005-09-22 18:31 ` Christoph Hellwig
2005-09-22 18:36 ` Jon Loeliger
2005-09-23 9:08 ` Christoph Hellwig
2005-09-23 12:54 ` Jon Loeliger [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=E1EIn4m-0001po-Bx@jdl.com \
--to=jdl@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppc64-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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