[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvwxQ2VeqkDpkiVks35DHxZFvAP5nKUtD7i4Z32291otOg@mail.gmail.com>
Date: Mon, 1 Aug 2011 19:52:35 +0200
From: richard -rw- weinberger <richard.weinberger@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: David Woodhouse <dwmw2@...radead.org>,
Arnaud Lacombe <lacombar@...il.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [PATCH 1/5] um: Use __i386__ in ifdef for vsyscall exports, not SUBARCH_i386
On Mon, Aug 1, 2011 at 6:32 AM, Al Viro <viro@...iv.linux.org.uk> wrote:
> Anyway, could you take a look at the git tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/um-header.git/,
> branch x86_merge and comment? It doesn't include stuff from this
> thread (yet); what it does is
> * further headers cleanups
> * sys-{i386,x86_64} merged; all[1] x86-specific code taken first
> to arch/um/sys-x86 and then (by final commit) to arch/x86/um. IMO that's
> the right place for it - target-dependent code is better off not hidden
> from maintainers of the target arch. When we get other ports to working
> shape, their target-specific parts ought to go into arch/<target>/um.
> * hopefully saner treatment of sigcontext; should make life easier
> for other ports.
>
> [1] theoretically - in reality we still have more than a few x86-isms in
> "generic" um headers in arch/um/include/asm.
>
Ok, will look at it in the next few days.
"sys-{i386,x86_64} merged" sounds great!
--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists