From d9a8cf803e9e001c2897f6fb23f7324f70a20dc0 Mon Sep 17 00:00:00 2001 From: William Tu Date: Mon, 30 Oct 2017 10:46:42 -0700 Subject: faq: Fix header path of ofp-msgs.h. Replace path 'lib/ofp-msgs.h' with 'include/openvswitch/ofp-msgs.h' Signed-off-by: William Tu Signed-off-by: Ben Pfaff --- Documentation/faq/contributing.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'Documentation') diff --git a/Documentation/faq/contributing.rst b/Documentation/faq/contributing.rst index df4eb9fac..e4a37708f 100644 --- a/Documentation/faq/contributing.rst +++ b/Documentation/faq/contributing.rst @@ -28,10 +28,11 @@ Development Q: How do I implement a new OpenFlow message? A: Add your new message to ``enum ofpraw`` and ``enum ofptype`` in - ``lib/ofp-msgs.h``, following the existing pattern. Then recompile and fix - all of the new warnings, implementing new functionality for the new message - as needed. (If you configure with ``--enable-Werror``, as described in - :doc:`/intro/install/general`, then it is impossible to miss any warnings.) + ``include/openvswitch/ofp-msgs.h``, following the existing pattern. + Then recompile and fix all of the new warnings, implementing new functionality + for the new message as needed. (If you configure with ``--enable-Werror``, as + described in :doc:`/intro/install/general`, then it is impossible to miss any + warnings.) To add an OpenFlow vendor extension message (aka experimenter message) for a vendor that doesn't yet have any extension messages, you will also need -- cgit v1.2.1