[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-api
Subject:    [PATCHv2 0/1] Document how to add a new syscall
From:       David Drysdale <drysdale () google ! com>
Date:       2015-07-30 7:52:10
Message-ID: 1438242731-27756-1-git-send-email-drysdale () google ! com
[Download RAW message or body]

Given that I've gotten some of the details wrong in the past (and I've
seen others do likewise), I thought it might be helpful to collate the
best practices for adding a new system call to the kernel.

Apologies for the wide circulation -- I've tried to include folk who've
recently added or proposed a system call, as they're most likely to
have opinions on:
 - whether this a useful addition to Documentation/
 - whether the details of the advice are correct and complete.

Thanks,
David

(With thanks to Andrew Morton for looking over an initial draft, and to
Michael Kerrisk for suggesting several clarifications and additions.)


Changes since v1:
 - added paragraph on build requirements to Testing section [Shuah Khan,
   Peter Zijlstra]
 - various text clarifications [Kees Cook]
 - added Reviewed-by markers


David Drysdale (1):
  Documentation: describe how to add a system call

 Documentation/adding-syscalls.txt | 463 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 463 insertions(+)
 create mode 100644 Documentation/adding-syscalls.txt

--
2.2.0.rc0.207.ga3a616c
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]