From: Mike Frysinger <vapier@gentoo.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: move ethtool include to where its used
Date: Sat, 4 Feb 2012 21:20:07 -0500 [thread overview]
Message-ID: <201202042120.14192.vapier@gentoo.org> (raw)
In-Reply-To: <20120204.162331.1482938799603820869.davem@davemloft.net>
[-- Attachment #1: Type: Text/Plain, Size: 1030 bytes --]
On Saturday 04 February 2012 16:23:31 David Miller wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > The linux/mii.h headers has long been standalone for userspace. But a
> > recent commit added linux/ethtool.h to the include list even when it
> > isn't used. Since we only need this with __KERNEL__, move the include
> > down to the right spot. Now userland no longer needs to pull this in.
>
> I don't understand what the problem is.
the exported linux/mii.h userspace code doesn't need linux/ethtool.h, thus it
should not need to include it
> linux/ethtool.h is a safely exported header file for userspace,
> so if linux/mii.h now starts to include it this should make no
> difference whatsoever for userspace unless userspace does something
> bogus which in turn would mean it's almost certainly userspace
> which is at fault here no the kernel headers.
by the same token, you could have linux/mii.h pointlessly include a lot of
other unused headers. they're still unused and a waste.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-05 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 11:17 [PATCH] net: move ethtool include to where its used Mike Frysinger
2012-02-04 21:23 ` David Miller
2012-02-05 2:20 ` Mike Frysinger [this message]
2012-02-05 5:24 ` 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=201202042120.14192.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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