All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Scott Wood <scottwood@freescale.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Avi Kivity <avi@redhat.com>, Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"qemu-devel" <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] Import Linux headers for KVM and vhost
Date: Tue, 3 May 2011 21:26:52 +0200	[thread overview]
Message-ID: <201105032126.53163.arnd@arndb.de> (raw)
In-Reply-To: <20110503125718.3e95f9ba@schlenkerla.am.freescale.net>

On Tuesday 03 May 2011 19:57:18 Scott Wood wrote:
> > I agree, it doesn't feel quite right to bring in the headers. I don't have
> > any alternative suggestions (besides better HOWTOs/Documentation) though. 
> 
> If you try to use the non-sanitized kernel headers, you'll get this warning
> from linux/types.h:
> 
> #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders"
> 

You're welcome ;-)

I tried to make the recommended approach as clear as I could with the
#warning and the wiki page. If there is anything still unclear about
how it should be done, please make suggestions for improving
the wiki text.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Scott Wood <scottwood@freescale.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, kvm <kvm@vger.kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>, Avi Kivity <avi@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] Import Linux headers for KVM and vhost
Date: Tue, 3 May 2011 21:26:52 +0200	[thread overview]
Message-ID: <201105032126.53163.arnd@arndb.de> (raw)
In-Reply-To: <20110503125718.3e95f9ba@schlenkerla.am.freescale.net>

On Tuesday 03 May 2011 19:57:18 Scott Wood wrote:
> > I agree, it doesn't feel quite right to bring in the headers. I don't have
> > any alternative suggestions (besides better HOWTOs/Documentation) though. 
> 
> If you try to use the non-sanitized kernel headers, you'll get this warning
> from linux/types.h:
> 
> #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders"
> 

You're welcome ;-)

I tried to make the recommended approach as clear as I could with the
#warning and the wiki page. If there is anything still unclear about
how it should be done, please make suggestions for improving
the wiki text.

	Arnd

  reply	other threads:[~2011-05-03 19:27 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 14:05 [RFC][PATCH] Import Linux headers for KVM and vhost Jan Kiszka
2011-05-03 14:05 ` [Qemu-devel] " Jan Kiszka
2011-05-03 15:12 ` Christoph Hellwig
2011-05-03 15:12   ` Christoph Hellwig
2011-05-03 15:32   ` Jan Kiszka
2011-05-03 15:32     ` Jan Kiszka
2011-05-03 15:41 ` Arnd Bergmann
2011-05-03 15:41   ` [Qemu-devel] " Arnd Bergmann
2011-05-03 16:48 ` [PATCH v2] " Jan Kiszka
2011-05-03 16:48   ` [Qemu-devel] " Jan Kiszka
2011-05-03 16:55   ` Avi Kivity
2011-05-03 16:55     ` [Qemu-devel] " Avi Kivity
2011-05-03 17:09     ` Jan Kiszka
2011-05-03 17:09       ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:13       ` Avi Kivity
2011-05-03 17:13         ` [Qemu-devel] " Avi Kivity
2011-05-03 17:32         ` Edgar E. Iglesias
2011-05-03 17:32           ` [Qemu-devel] " Edgar E. Iglesias
2011-05-03 17:39           ` Jan Kiszka
2011-05-03 17:39             ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:57           ` Scott Wood
2011-05-03 17:57             ` Scott Wood
2011-05-03 19:26             ` Arnd Bergmann [this message]
2011-05-03 19:26               ` Arnd Bergmann
2011-05-03 17:30   ` Peter Maydell
2011-05-03 17:30     ` Peter Maydell
2011-05-03 17:42     ` Jan Kiszka
2011-05-03 17:42       ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:45     ` Anthony Liguori
2011-05-03 17:45       ` Anthony Liguori
2011-05-03 17:55       ` Jan Kiszka
2011-05-03 17:55         ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:59         ` Anthony Liguori
2011-05-03 17:59           ` Anthony Liguori
2011-05-03 21:37           ` Michael S. Tsirkin
2011-05-03 21:37             ` [Qemu-devel] " Michael S. Tsirkin
2011-05-04  8:55             ` Jan Kiszka
2011-05-04  8:55               ` [Qemu-devel] " Jan Kiszka
2011-05-09  3:24               ` Rusty Russell
2011-05-09  3:24                 ` [Qemu-devel] " Rusty Russell
2011-05-03 20:22   ` Peter Maydell
2011-05-03 20:22     ` Peter Maydell
2011-05-04 10:28     ` Jan Kiszka
2011-05-04 10:28       ` [Qemu-devel] " Jan Kiszka
2011-05-04 17:58       ` Andreas Färber
2011-05-04 18:01         ` Jan Kiszka
2011-05-04 18:01           ` [Qemu-devel] " Jan Kiszka

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=201105032126.53163.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.