From: Dave Hansen <dave@sr71.net>
To: mtk.manpages@gmail.com
Cc: lkml <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"x86@kernel.org" <x86@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/7] System Calls for Memory Protection Keys
Date: Thu, 3 Mar 2016 15:49:11 -0800 [thread overview]
Message-ID: <56D8CD77.1090603@sr71.net> (raw)
In-Reply-To: <CAKgNAkjaZvR-Csf5eEBVi+Eo1HjeXH7Kg0LUL=i1Q-HAJ1EP-A@mail.gmail.com>
On 03/03/2016 12:05 AM, Michael Kerrisk (man-pages) wrote:
>> > I have manpages written for some of these syscalls, and I will
>> > submit a full set of manpages once we've reached some consensus
>> > on what the interfaces should be.
> Please don't do things in this order. Providing man pages up front
> make it easier for people to understand, review, and critique the API.
> Submitting man pages should be a foundational part of submitting a new
> set of interfaces and discussing their design.
Michael, thanks for taking a look, plus the very detailed previous
review you did of the first batch of man-pages that I posted.
I've posted a newer version including all of the new system calls, and
I've attempted to address all the earlier review comments you made.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@sr71.net>
To: mtk.manpages@gmail.com
Cc: lkml <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"x86@kernel.org" <x86@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/7] System Calls for Memory Protection Keys
Date: Thu, 3 Mar 2016 15:49:11 -0800 [thread overview]
Message-ID: <56D8CD77.1090603@sr71.net> (raw)
In-Reply-To: <CAKgNAkjaZvR-Csf5eEBVi+Eo1HjeXH7Kg0LUL=i1Q-HAJ1EP-A@mail.gmail.com>
On 03/03/2016 12:05 AM, Michael Kerrisk (man-pages) wrote:
>> > I have manpages written for some of these syscalls, and I will
>> > submit a full set of manpages once we've reached some consensus
>> > on what the interfaces should be.
> Please don't do things in this order. Providing man pages up front
> make it easier for people to understand, review, and critique the API.
> Submitting man pages should be a foundational part of submitting a new
> set of interfaces and discussing their design.
Michael, thanks for taking a look, plus the very detailed previous
review you did of the first batch of man-pages that I posted.
I've posted a newer version including all of the new system calls, and
I've attempted to address all the earlier review comments you made.
next prev parent reply other threads:[~2016-03-03 23:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 1:11 [RFC][PATCH 0/7] System Calls for Memory Protection Keys Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-02-23 1:11 ` [RFC][PATCH 1/7] x86, pkeys: Documentation Dave Hansen
2016-02-23 1:11 ` [RFC][PATCH 2/7] mm: implement new pkey_mprotect() system call Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-02-23 1:11 ` [RFC][PATCH 3/7] x86, pkeys: make mprotect_key() mask off additional vm_flags Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-02-23 1:11 ` [RFC][PATCH 4/7] x86: wire up mprotect_key() system call Dave Hansen
2016-02-23 1:11 ` Dave Hansen
[not found] ` <20160223011107.FB9B8215-LXbPSdftPKxrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-02-23 1:11 ` [RFC][PATCH 5/7] x86, pkeys: allocation/free syscalls Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-03-03 8:05 ` [RFC][PATCH 0/7] System Calls for Memory Protection Keys Michael Kerrisk (man-pages)
2016-03-03 8:05 ` Michael Kerrisk (man-pages)
2016-03-03 8:05 ` Michael Kerrisk (man-pages)
2016-03-03 23:49 ` Dave Hansen [this message]
2016-03-03 23:49 ` Dave Hansen
2016-02-23 1:11 ` [RFC][PATCH 6/7] x86, pkeys: add pkey set/get syscalls Dave Hansen
2016-02-23 1:11 ` Dave Hansen
2016-02-23 6:45 ` Ingo Molnar
2016-02-23 6:45 ` Ingo Molnar
2016-02-23 1:11 ` [RFC][PATCH 7/7] pkeys: add details of system call use to Documentation/ Dave Hansen
2016-02-23 1:11 ` Dave Hansen
[not found] ` <20160223011118.954E64B7-LXbPSdftPKxrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-02-23 6:38 ` Ingo Molnar
2016-02-23 6:38 ` Ingo Molnar
2016-02-23 6:38 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D8CD77.1090603@sr71.net \
--to=dave@sr71.net \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.