From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: mike.mclagan@linux.org, Ingo Molnar <mingo@elte.hu>,
Sam Ravnborg <sam@ravnborg.org>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: why usr/include/linux/if_frad.h is required
Date: Tue, 20 Jan 2009 20:22:54 +0530 [thread overview]
Message-ID: <1232463174.3088.15.camel@localhost.localdomain> (raw)
For if_frad.h I am getting two warnings with 'make headers_check':
usr/include/linux/if_frad.h:29: leaks CONFIG_DLCI to userspace where it is not valid
usr/include/linux/if_frad.h:129: leaks CONFIG_DLCI to userspace where it is not valid
Almost all if_frad.h is covered with #if defined(CONFIG_DLCI) || defined(CONFIG_DLCI_MODULE)
If I remove this portion so only this what we get in userspace:
#ifndef _FRAD_H_
#define _FRAD_H_
#include <linux/if.h>
#endif
So I am surprising what is the point of this ?
Can I change its name to is_fraud ;-)
--
JSR
next reply other threads:[~2009-01-20 14:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 14:52 Jaswinder Singh Rajput [this message]
2009-01-20 14:54 ` why usr/include/linux/if_frad.h is required Jaswinder Singh Rajput
2009-01-20 17:47 ` Arnd Bergmann
2009-01-20 19:53 ` Krzysztof Halasa
2009-01-20 23:48 ` Jaswinder Singh Rajput
2009-01-21 1:06 ` Krzysztof Halasa
2009-01-21 4:50 ` Jaswinder Singh Rajput
2009-01-21 5:33 ` Sam Ravnborg
2009-01-21 6:15 ` David Miller
2009-01-21 6:38 ` Stephen Hemminger
2009-01-21 23:37 ` David Miller
2009-01-22 5:37 ` Sam Ravnborg
2009-01-24 13:25 ` Jaswinder Singh Rajput
2009-01-24 15:32 ` Krzysztof Halasa
2009-01-26 20:30 ` David Miller
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=1232463174.3088.15.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=davem@davemloft.net \
--cc=mike.mclagan@linux.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
/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).