From: Anthony Liguori <anthony@codemonkey.ws>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-linux.c: #define __user to work around broken Linux headers
Date: Thu, 28 Aug 2008 15:49:14 -0500 [thread overview]
Message-ID: <48B70F4A.5030802@codemonkey.ws> (raw)
In-Reply-To: <20080828204114.GD3229@networkno.de>
Thiemo Seufer wrote:
> Anthony Liguori wrote:
>
> It was rejected because distros should fix their broken headers instead.
>
In all fairness the headers in /usr/include/linux are not meant for
application consumption. The are for private use by glibc.
Applications are suppose to copy and fixup Linux headers into their
local trees.
Regards,
Anthony Liguori
> Thiemo
>
next prev parent reply other threads:[~2008-08-28 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:24 [Qemu-devel] [PATCH] usb-linux.c: #define __user to work around broken Linux headers Ian Jackson
2008-08-28 20:06 ` Anthony Liguori
2008-08-28 20:41 ` Thiemo Seufer
2008-08-28 20:49 ` Anthony Liguori [this message]
2008-08-29 9:47 ` Ian Jackson
2008-09-07 2:50 ` Anthony Liguori
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=48B70F4A.5030802@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).