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
• Backporting patches
  • Changes to userspace components
  • Changes to Linux kernel components
• 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
  • Libraries
• Windows Datapath Coding Style
  • Basics
  • Types
  • Naming
  • Comments
  • Functions
  • Source Files
• Documentation Style
  • reStructuredText vs. Sphinx
  • rST Conventions
  • Man Pages
  • Writing Style
  • Helpful Tools
  • Useful Links
• Open vSwitch Library ABI Updates
  • Definitions
  • Overview
  • ABI Policy
  • Coding

Submitting Patches ›

‹ Open vSwitch Internals

Contents

• Project

• Getting Started
• Tutorials
• How-to Guides
• Deep Dive
• Reference Guide
• Open vSwitch Internals
  • Contributing to Open vSwitch
    • Submitting Patches
    • Backporting patches
    • Coding Style
    • Windows Datapath Coding Style
    • Documentation Style
    • Open vSwitch Library ABI Updates
  • Mailing Lists
  • Patchwork
  • Release Process
  • Reporting Bugs
  • Security Process
  • The Linux Foundation Open vSwitch Project Charter
  • Emeritus Status for OVS Committers
  • Expectations for Developers with Open vSwitch Repo Access
  • OVS Committer Grant/Revocation Policy
  • Authors
  • Committers
  • How Open vSwitch’s Documentation Works
• Open vSwitch Documentation
• FAQ

Browse

• General Index
• Submitting Patches
• Open vSwitch Internals

Navigation

• Open vSwitch 3.2.90 documentation
  • Open vSwitch Internals
    • Contributing to Open vSwitch