From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: jpirko@redhat.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org,
eric.dumazet@gmail.com, linville@tuxdriver.com, kaber@trash.net
Subject: Re: net-next-2.6 status...
Date: Wed, 16 Mar 2011 11:17:36 -0700 (PDT) [thread overview]
Message-ID: <20110316.111736.48500809.davem@davemloft.net> (raw)
In-Reply-To: <1300299219.2811.7.camel@bwh-desktop>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 16 Mar 2011 18:13:39 +0000
> Though, in this case, the priv_flags are not in any way visible to
> user-space, so it would be quite hard to find a use for them!
There are pieces of infrastructure, such as scripts that turn header
file visible macro values into values usable in other languages such
as perl, that do that wholesale for entire header files and therefore
expect these individual values to be there.
I'm not going to be the person who breaks such things.
next prev parent reply other threads:[~2011-03-16 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 23:01 net-next-2.6 status David Miller
[not found] ` <20110315.160124.104058374.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-03-16 0:13 ` John W. Linville
2011-03-16 0:36 ` Jeff Kirsher
2011-03-16 6:50 ` Jiri Pirko
2011-03-16 7:02 ` David Miller
2011-03-16 7:38 ` Jiri Pirko
[not found] ` <20110316073803.GB2780-YzwxZg+R7et1/kRsl7OVgNvLeJWuRmrY@public.gmane.org>
2011-03-16 8:40 ` Jiri Pirko
2011-03-16 8:47 ` Thomas Graf
[not found] ` <20110316084739.GD26145-oJAMn8VJQk8CUdFEqe4BF2D2FQJk+8+b@public.gmane.org>
2011-03-16 17:38 ` David Miller
2011-03-16 17:42 ` David Miller
2011-03-16 18:13 ` Ben Hutchings
2011-03-16 18:17 ` David Miller [this message]
2011-03-16 17:38 ` David Miller
[not found] ` <20110316.103857.226773145.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-03-16 17:56 ` Jiri Pirko
2011-03-16 18:00 ` 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=20110316.111736.48500809.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=eric.dumazet@gmail.com \
--cc=jpirko@redhat.com \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).