From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86: more header untangling
Date: Wed, 11 Feb 2009 10:55:00 -0800 [thread overview]
Message-ID: <49931F04.80605@goop.org> (raw)
In-Reply-To: <20090211171439.GA9185@elte.hu>
Ingo Molnar wrote:
> constants can be considered data types too.
Huh, that's a pretty broad definition of "type", to the degree that's
its fairly counter-intuitive and misleading. But I don't care that much.
> Small inlines are borderlines,
> they should generally not be in _types.h headers. Really, _types.h headers
> are only there to instantiate a type, to enable dependent inline methods
> to use them.
>
In this case the inlines are the accessor functions to do the pte_t <->
pteval_t (un)wrapping. They're trivial and have no dependencies apart
from the types they're right next to.
Anyway, check out
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
x86/untangle now. I had to merge in tip/x86/paravirt to get the
pte_flags changes I made there, and unfortunately it didn't merge
completely cleanly, so there's probably some spurious changes in there.
I guess I can respin it into a clean branch.
J
next prev parent reply other threads:[~2009-02-11 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 19:31 [GIT PULL] x86: more header untangling Jeremy Fitzhardinge
2009-02-11 10:03 ` Ingo Molnar
2009-02-11 17:01 ` Jeremy Fitzhardinge
2009-02-11 17:14 ` Ingo Molnar
2009-02-11 18:55 ` Jeremy Fitzhardinge [this message]
2009-02-11 19:47 ` Ingo Molnar
2009-02-11 22:34 ` Jeremy Fitzhardinge
2009-02-13 11:47 ` Ingo Molnar
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=49931F04.80605@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@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