From: Jiri Pirko <jpirko@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: 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 18:56:44 +0100 [thread overview]
Message-ID: <20110316175642.GB2867@psychotron.redhat.com> (raw)
In-Reply-To: <20110316.103857.226773145.davem@davemloft.net>
Wed, Mar 16, 2011 at 06:38:57PM CET, davem@davemloft.net wrote:
>From: Jiri Pirko <jpirko@redhat.com>
>Date: Wed, 16 Mar 2011 08:38:03 +0100
>
>> Wed, Mar 16, 2011 at 08:02:51AM CET, davem@davemloft.net wrote:
>>>From: Jiri Pirko <jpirko@redhat.com>
>>>Date: Wed, 16 Mar 2011 07:50:09 +0100
>>>
>>>>>Jiri, I know there is your patch set there, but I think you and Changli
>>>>>still need to go back and forth one more time wrt. orig_dev semantics.
>>>>>Since you have been posting this patch set for some time I'm still
>>>>>willing to apply it for this merge window, but please make haste and
>>>>>work out the remaining discussion. Thank you.
>>>>
>>>> Dave, you can apply the rest of the series and leave only the first
>>>> patch (af_packet) out. There's no dependency. We will figure out things
>>>> around origdev later.
>>>
>>>I was about to do that but I've found other problems.
>>>
>>>You cannot make the modifications you make to linux/if.h, those
>>>interface flags are visible to userspace.
>>
>> What do you suggest? To remove unused flags and leave gaps there or to
>> not to remove the flags at all?
>
>You can't remove them, otherwise if it happened to be reference in the
>sources to some app out there, it will start to fail to compile.
>
>This is pretty obvious stuff, I hope :-)
Ok :( So would you leave out if.h hunk out or should I repost?
next prev parent reply other threads:[~2011-03-16 18:56 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
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
2011-03-16 8:40 ` Jiri Pirko
2011-03-16 8:47 ` Thomas Graf
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
2011-03-16 17:38 ` David Miller
2011-03-16 17:56 ` Jiri Pirko [this message]
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=20110316175642.GB2867@psychotron.redhat.com \
--to=jpirko@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.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