Contributing to Open vSwitch

The below guides provide information on contributing to Open vSwitch itself.

• Submitting Patches
  • Before You Start
  • Email Subject
  • Description
  • Tags
  • Developer’s Certificate of Origin
  • Feature Deprecation Guidelines
  • Comments
  • Patch
  • Example
• Open vSwitch Coding Style
  • Basics
  • Naming
  • Comments
  • Functions
  • Function Prototypes
  • Statements
  • Return Values
  • Macros
  • Thread Safety Annotations
  • Source Files
  • Header Files
  • Types
  • Expressions
  • Blank Lines
  • C DIALECT
  • Python
• Open vSwitch Windows Datapath Coding Style
  • Basics
  • Types
  • Naming
  • Comments
  • Functions
  • Source Files
• Open vSwitch Documentation Style
  • reStructuredText vs. Sphinx
  • reST Conventions
  • Writing Style
  • Helpful Tools
  • Useful Links

Submitting Patches ›

‹ Open vSwitch Internals

Contents

• Open vSwitch Documentation

• Getting Started
• Tutorials
• Open vSwitch Deep Dive
• How-to Guides
• Reference Guide
• Open vSwitch FAQ
• Open vSwitch Internals
  • Contributing to Open vSwitch
    • Submitting Patches
    • Open vSwitch Coding Style
    • Open vSwitch Windows Datapath Coding Style
    • Open vSwitch Documentation Style
  • Mailing Lists
  • Patchwork
  • Open vSwitch Release Process
  • Reporting Bugs in Open vSwitch
  • Open vSwitch’s Security Process
  • Expectations for Developers with Open vSwitch Repo Access
  • OVS Committer Grant/Revocation Policy
  • Authors
  • Committers

Browse

• General Index
• Submitting Patches
• Open vSwitch Internals

Navigation

• Open vSwitch 2.6.0 documentation
  • Open vSwitch Internals
    • Contributing to Open vSwitch