GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • The Linux Kernel
  • Development process
  • Submitting patches
  • Code of conduct
  • Maintainer handbook
  • All development-process docs
  • HOWTO do Linux kernel development
  • Linux Kernel patch submission checklist
  • Minimal requirements to compile the Kernel
  • Programming Language
  • Linux kernel coding style
  • Kernel Maintainer PGP guide
  • Email clients info for Linux
  • Applying Patches To The Linux Kernel

This view

  • Original page
  • New address

GeezerVison is showing origin.kernel.org — Working with the kernel development community — The Linux Kernel documentation

English
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Italian
  • Portuguese (Brazilian)
  • Spanish

Working with the kernel development community¶

So you want to be a Linux kernel developer? Welcome! While there is a lot to be learned about the kernel in a technical sense, it is also important to learn about how our community works. Reading these documents will make it much easier for you to get your changes merged with a minimum of trouble.

An introduction to how kernel development works¶

Read these documents first: an understanding of the material here will ease your entry into the kernel community.

  • HOWTO do Linux kernel development
  • A guide to the Kernel Development Process
  • Submitting patches: the essential guide to getting your code into the kernel
  • Linux Kernel patch submission checklist

Tools and technical guides for kernel developers¶

This is a collection of material that kernel developers should be familiar with.

  • Minimal requirements to compile the Kernel
  • Programming Language
  • Linux kernel coding style
  • Kernel Maintainer PGP guide
  • Email clients info for Linux
  • Applying Patches To The Linux Kernel
  • Backporting and conflict resolution
  • Adding a New System Call
  • Why the “volatile” type class should not be used
  • (How to avoid) Botching up ioctls

Policy guides and developer statements¶

These are the rules that we try to live by in the kernel community (and beyond).

  • Linux kernel licensing rules
  • Contributor Covenant Code of Conduct
  • Linux Kernel Contributor Covenant Code of Conduct Interpretation
  • Linux Kernel Contribution Maturity Model
  • Linux Kernel Enforcement Statement
  • Kernel Driver Statement
  • The Linux Kernel Driver Interface
  • Everything you ever wanted to know about Linux -stable releases
  • Linux kernel management style
  • Researcher Guidelines
  • Kernel Guidelines for Tool-Generated Content
  • AI Coding Assistants
  • Linux kernel project continuity

Dealing with bugs¶

Bugs are a fact of life; it is important that we handle them properly. The documents below provide general advice about debugging and describe our policies around the handling of a couple of special classes of bugs: regressions and security problems.

  • Debugging advice for Linux Kernel developers
  • Handling regressions
  • Security bugs
  • The Linux Kernel threat model
  • CVEs
  • Embargoed hardware issues

Maintainer information¶

How to find the people who will accept your patches.

  • Subsystem and maintainer tree specific development process notes
  • List of maintainers

Other material¶

Here are some other guides to the community that are of interest to most developers:

  • Index of Further Kernel Documentation
  • Deprecated Interfaces, Language Features, Attributes, and Conventions
©The kernel development community. | Powered by Sphinx 5.3.0 & Alabaster 0.7.16 | Page source
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.