netdev - Re: [PATCHv2] iproute2: generalize VXLAN forwarding tables

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 26 Apr 2013 13:08:17 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	David Stevens <dlstevens@...ibm.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCHv2] iproute2: generalize VXLAN forwarding tables

On Fri, 26 Apr 2013 10:07:17 -0400
David Stevens <dlstevens@...ibm.com> wrote:

> Stephen,
>         I assume you mean below that you're waiting for net-next changes 
> to
> be merged in Linus' tree for your build, but to be honest I'm not sure how 
> I can
> tell if this has happened or not. Do you do announcements for opening up
> 3.10 iproute2, or should I be watching a particular Linus git tree for the 
> include
> file changes?
>         I'd guess this is open again by now, and if so, I can merge and 
> resubmit,
> but I'd like to know for the future how I should time iproute2 
> submissions, so that
> you have the needed include file changes before I submit. Or, if you're 
> doing
> announcements, I can tweak my mail filters to make sure I see them.
>         Sorry if this is a newbie question or is covered in a FAQ 
> somewhere--
> it just never came up for me before.
>                                                 thanks,
>                                                         +-DLS

Up until now, I have mostly been lazy and only one branch of iproute2.
The master corresponds to the current Linus kernel headers and features.
Then I would collect patches during the merge window of the next release.
This is because the number of new features going into iproute2 was limited to 1 or 2
per release. But the speed is accelerating.

For next-release, I will split this into
  master == davem net == linus
  net-next == davem net-next
Which will mean more work for me and submitters (getting right branch), but
will make sure stuff doesn't get held out for so long.


Not changing right now, but will start after 3.10
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html