From: David Miller <davem@davemloft.net>
To: dwmw2@infradead.org
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
kirill@shutemov.name
Subject: Re: [PATCH] wireless.h: improve userland include-ability
Date: Wed, 04 Jun 2008 08:02:37 -0700 (PDT) [thread overview]
Message-ID: <20080604.080237.66646394.davem@davemloft.net> (raw)
In-Reply-To: <1212587529.32207.82.camel@pmac.infradead.org>
From: David Woodhouse <dwmw2@infradead.org>
Date: Wed, 04 Jun 2008 14:52:09 +0100
> On Tue, 2008-06-03 at 12:05 -0700, David Miller wrote:
> > Yeah, go check so me magic userspace tool header to see what magic is
> > needed just to include a core networking header file correctly.
> >
> > No, thanks.
>
> Just to clarify: this is only a problem for userspace, and you're
> objecting to that?
Yes.
> I'm happy enough to change that, but it means seeing stuff like...
> #ifndef __KERNEL__
> #include <sys/foo.h>
> #endif
> ... in kernel headers. Is that what you're intending, or am I
> misunderstanding your objection?
I think this kind of construct shouldn't be necessary in the first
place.
> I believe that the main reason for this patch was that <linux/socket.h>
> and <linux/if.h> both have problems when you include them in the same C
> file as the 'proper' glibc equivalent? Is that something we can address,
> instead of just dropping those includes?
You will need to find a way to make it work cleanly if you want
me to take the change in :-)
next prev parent reply other threads:[~2008-06-04 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 17:51 [PATCH] wireless.h: improve userland include-ability John W. Linville
2008-06-03 19:05 ` David Miller
2008-06-04 13:52 ` David Woodhouse
2008-06-04 14:23 ` Kirill A. Shutemov
2008-06-04 14:26 ` David Woodhouse
2008-06-04 14:56 ` David Woodhouse
2008-06-04 15:02 ` David Miller [this message]
2008-06-04 15:26 ` David Woodhouse
2008-06-04 15:47 ` David Miller
2008-06-04 15:50 ` David Woodhouse
2008-06-04 15:24 ` Pavel Roskin
2008-06-04 17:34 ` John W. Linville
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=20080604.080237.66646394.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=kirill@shutemov.name \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).