From: Christoph Hellwig <hch@infradead.org>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: xen-devel@lists.xensource.com,
lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
Dave Hansen <haveblue@us.ibm.com>
Subject: Re: [ PATCH 2.6.16-rc3-xen 1/3] sysfs: export Xen hypervisor attributes to sysfs
Date: Tue, 21 Feb 2006 17:42:16 +0000 [thread overview]
Message-ID: <20060221174216.GA26784@infradead.org> (raw)
In-Reply-To: <43FB2573.3070909@us.ibm.com>
> Patch 1 (this patch) is a Xen file that is used by all OS kernels that run
> on Xen. This includes linux, NetBSD, FreeBSD, Solaris, and others. Patch 1
> adds #defined constants so that linux users of this file can avoid
> typedefs.
No way we're gonna put in that crap. If you want linux to support Xen
add a set of sane linux-style headers for linux use. What you use
in the hypevisor or for other operating systems doesn't matter at all.
next prev parent reply other threads:[~2006-02-21 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 14:36 [ PATCH 2.6.16-rc3-xen 1/3] sysfs: export Xen hypervisor attributes to sysfs Mike D. Day
2006-02-21 15:21 ` Arjan van de Ven
2006-02-21 17:37 ` [Xen-devel] " Keir Fraser
2006-02-21 17:42 ` Christoph Hellwig [this message]
2006-02-21 17:56 ` Greg KH
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=20060221174216.GA26784@infradead.org \
--to=hch@infradead.org \
--cc=greg@kroah.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncmike@us.ibm.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