summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorWilliam Tu <u9012063@gmail.com>2017-10-30 10:46:42 -0700
committerBen Pfaff <blp@ovn.org>2017-10-30 10:50:22 -0700
commitd9a8cf803e9e001c2897f6fb23f7324f70a20dc0 (patch)
tree69ec0cc6c69a1ba49d78b0428a9998f0d5270e33 /Documentation
parentb05af21631ce03e8c4594709dee1651268a028f0 (diff)
downloadopenvswitch-d9a8cf803e9e001c2897f6fb23f7324f70a20dc0.tar.gz
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 <u9012063@gmail.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/faq/contributing.rst9
1 files changed, 5 insertions, 4 deletions
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