From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] apic: clean up msr handling
Date: Fri, 11 Jun 2010 17:48:46 +0100 [thread overview]
Message-ID: <C838277E.175BB%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <201006111810.20689.Christoph.Egger@amd.com>
On 11/06/2010 17:10, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> But this is not what I meant by 'clean up the headers'.
> For example, when you do
>
> touch xen/include/asm-x86/apic.h
>
> then in the next build files that have nothing to do with
> apic get recompiled because apic.h is indirectly included.
Yeah, smp.h should not need to include apic.h. I fixed this up as
xen-unstable:21608.
-- Keir
prev parent reply other threads:[~2010-06-11 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 13:22 [PATCH] apic: clean up msr handling Christoph Egger
2010-06-11 13:40 ` Jan Beulich
2010-06-11 13:49 ` Keir Fraser
2010-06-11 15:51 ` Christoph Egger
2010-06-11 15:57 ` Keir Fraser
2010-06-11 16:10 ` Christoph Egger
2010-06-11 16:48 ` Keir Fraser [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=C838277E.175BB%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).