I tested ARP with stable/1801 and it works fine
23:20:10.885539 ARP, Request who-has 3.3.3.5 tell 3.3.3.1, length 28
23:20:10.885769 ARP, Reply 3.3.3.5 is-at 08:00:27:c9:ea:36 (oui Unknown),
length 46
Matus
From: 李洪亮 [mailto:lihongli...@360.cn]
Sent: Friday, December 22, 2017 4:36 PM
To: Matus
+1 for Hongjun
Best Regards,
Anna
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Zhou, Danny
Sent: Friday, January 5, 2018 11:14 AM
To: a...@yunify.org; t...@lists.fd.io; nsh_sfc-...@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] [nsh_sfc-dev]
You are right George and Ash. The process, as pointed by Ed to me before, is
at https://fd.io/governance/technical-community-charter/#tcc323.
Below are current committers of NSH_SFC project who are eligible to vote.
[cid:image003.jpg@01D38616.1DC41AB0]
From: George Zhao
Hi Danny,
Thanks for your contributions.
I will let Ed correct me if I am wrong, I don’t think PTL need TSC approval,
but an email thread from project committers voted +1 for Honghui Ni as new PTL.
BR,
George
From: tsc-boun...@lists.fd.io [mailto:tsc-boun...@lists.fd.io] On Behalf Of
Folks,
Just a reminder of VPP 18.01 Release Milestones:
https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.01#Release_Milestones
VPP 18.01 RC2 is next Wednesday January 10, 2018.
Per the standard process, all bug fixes to the stable branch should
follow the best practices:
Folks,
The VPP 18.01 RC1 milestone is complete. The VPP 18.01 release
branch(stable/1801) has been created, along with the associated nexus
and packagecloud repo's.
* vpp master branch is now open for all patches slated for VPP 18.04
(and beyond).
* vpp stable/1801 is open for bug fix
All of the pool_get(mypool, new_elt) variants are capable of expanding - and
hence moving - mypool, leading to dangling references to free memory if you’re
not careful. Here’s the usual coding pattern:
old_elt = pool_elt_at_index (mypool, index);
/* use old-elt */
pool_get (mypool, new_elt);
