Ben, we'll send out new patch series based on the recently merged patches and new PTAP series, sending this in the very early phase was just to get some general comments about implementation, Jan has reviewed them and changed many things per his full ovs experience, so next post will have high quality.
-----Original Message----- From: Ben Pfaff [mailto:[email protected]] Sent: Wednesday, June 7, 2017 2:17 AM To: Yang, Yi Y <[email protected]> Cc: [email protected] Subject: Re: [ovs-dev] [RFC PATCH 0/2] Generic encap/decap actions implementation On Thu, Apr 20, 2017 at 11:26:39AM +0800, Yi Yang wrote: > This patchset implements "Generic encap/decap actions" (EXT-382), it > is based on top of the below patchsets: > > [PATCH v1 0/5] NSH userspace support > https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/331158.html > > [PATCH 0/10] userspace: Packet type-aware pipeline > https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/331023.html > > [PATCH v3 0/8] userspace: Support for L3 tunnelin > https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330488.html Hi, thanks for posting this. It's difficult to deal with multiple dependent patch series. In practice, I don't usually even read patch series that depend on others, because it means that there are multiple steps to get to them. To get a better chance for review, I suggest putting all of the patches together into a single series. In case it is part of your concern, it's no problem to have RFC or experimental patches at the end of a series that is otherwise ready for review. Thanks, Ben. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
