From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Drysdale Subject: [PATCH RFC 0/1] Document how to add a new syscall Date: Tue, 28 Jul 2015 12:41:02 +0100 Message-ID: <1438083663-24814-1-git-send-email-drysdale@google.com> Return-path: Sender: linux-doc-owner@vger.kernel.org To: linux-api@vger.kernel.org, Michael Kerrisk , Andrew Morton , Arnd Bergmann , Shuah Khan , Jonathan Corbet Cc: Andrea Arcangeli , Thomas Gleixner , Eric B Munson , Ingo Molnar , "H. Peter Anvin" , Oleg Nesterov , Linus Torvalds , Greg Kroah-Hartman , Andy Lutomirski , Al Viro , Rusty Russell , Peter Zijlstra , Vivek Goyal , Alexei Starovoitov , David Herrmann , Theodore Ts'o , Kees Cook , Miklos Szeredi , Milosz Tanski , Fam Zheng , Josh Triplett , Mathieu Desnoyers , linux-doc@vger.kernel.org, linux-kernel@vger.ke List-Id: linux-api@vger.kernel.org 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. Shuah, is there anything more that should be added for the Testing section in particular? Thanks, David (With thanks to Andrew Morton for looking over an initial draft, and to Michael Kerrisk for suggesting several clarifications and additions.) David Drysdale (1): Documentation: describe how to add a system call Documentation/adding-syscalls.txt | 454 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 454 insertions(+) create mode 100644 Documentation/adding-syscalls.txt -- 2.2.0.rc0.207.ga3a616c