diff options
| -rw-r--r-- | AUTHORS.rst | 1 | ||||
| -rw-r--r-- | Documentation/faq/contributing.rst | 10 |
2 files changed, 6 insertions, 5 deletions
diff --git a/AUTHORS.rst b/AUTHORS.rst index e17daf078..a7cba9586 100644 --- a/AUTHORS.rst +++ b/AUTHORS.rst @@ -376,6 +376,7 @@ Aaron M. Ucko ucko@debian.org Abhinav Singhal Abhinav.Singhal@spirent.com Adam Heath doogie@brainfood.com Ahmed Bilal numan252@gmail.com +Alan Kayahan hsykay@gmail.com Alan Shieh ashieh@nicira.com Alban Browaeys prahal@yahoo.com Alex Yip alex@nicira.com 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 |