diff options
author | Ben Pfaff <blp@ovn.org> | 2018-01-02 10:49:41 -0800 |
---|---|---|
committer | Ben Pfaff <blp@ovn.org> | 2018-01-02 10:49:41 -0800 |
commit | e9de6c060e3c2404c7c77e2340ee2b1a90f78a1b (patch) | |
tree | 83d5f34ae0ce38631c26803bb11a939918cf4ffb /Documentation | |
parent | bcc3a94018cf14e142f907a66636060b13a0f0ec (diff) | |
download | openvswitch-e9de6c060e3c2404c7c77e2340ee2b1a90f78a1b.tar.gz |
faq: Correct location of flow.h.
Reported-by: Alan Kayahan <hsykay@gmail.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
Reviewed-by: Greg Rose <gvrose8192@gmail.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/faq/contributing.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/faq/contributing.rst b/Documentation/faq/contributing.rst index e4a37708f..d5226f4f7 100644 --- a/Documentation/faq/contributing.rst +++ b/Documentation/faq/contributing.rst @@ -45,11 +45,11 @@ Q: How do I implement a new OpenFlow message? Q: How do I add support for a new field or header? - A: Add new members for your field to ``struct flow`` in ``lib/flow.h``, and - add new enumerations for your new field to ``enum mf_field_id`` in - ``include/openvswitch/meta-flow.h``, following the existing pattern. If - the field uses a new OXM class, add it to OXM_CLASSES in - ``build-aux/extract-ofp-fields``. Also, add support to + A: Add new members for your field to ``struct flow`` in + ``include/openvswitch/flow.h``, and add new enumerations for your new field + to ``enum mf_field_id`` in ``include/openvswitch/meta-flow.h``, following + the existing pattern. If the field uses a new OXM class, add it to + OXM_CLASSES in ``build-aux/extract-ofp-fields``. Also, add support to ``miniflow_extract()`` in ``lib/flow.c`` for extracting your new field from a packet into struct miniflow, and to ``nx_put_raw()`` in ``lib/nx-match.c`` to output your new field in OXM matches. Then recompile |