From: Christoph Egger <Christoph.Egger@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xensource.com, Pat Campbell <plc@novell.com>
Subject: Re: build problem with new ioemu
Date: Fri, 18 Jul 2008 15:13:14 +0200 [thread overview]
Message-ID: <200807181513.14561.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C4A65456.24490%keir.fraser@eu.citrix.com>
On Friday 18 July 2008 15:08:22 Keir Fraser wrote:
> On 18/7/08 13:59, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> >> Old code did:
> >> /* Some versions of usbdevice_fs.h need __user to be defined for them.
> >> */ /* This may (harmlessly) conflict with a definition in
> >> linux/compiler.h. */ #define __user
> >> #include <linux/usbdevice_fs.h>
> >>
> >> Not sure which is the better solution
> >>
> >> Pat
> >
> > This patch works. Tnx.
> >
> > Keir: Please apply it.
>
> IanJ is on it.
Ok.
> The old approach is better than linux/compiler.h since not all systems have
> that header (and if they do, may not define __user).
Right. In particular the non-LInux systems don't have any <linux/*>
header. ;-)
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-07-18 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 12:10 build problem with new ioemu Christoph Egger
2008-07-18 13:00 ` Pat Campbell
2008-07-18 12:59 ` Christoph Egger
2008-07-18 13:08 ` Keir Fraser
2008-07-18 13:13 ` Christoph Egger [this message]
2008-07-18 13:15 ` Keir Fraser
2008-07-18 14:47 ` Ian Jackson
2008-07-18 14:52 ` Ian Jackson
2008-07-18 14:44 ` Ian Jackson
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=200807181513.14561.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=plc@novell.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 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.