Date: Mon, 29 Oct 2018 21:05:22 +0200 From: Igor Stoppa <igor.stoppa@...il.com> To: Mike Rapoport <rppt@...ux.ibm.com> Cc: Mimi Zohar <zohar@...ux.vnet.ibm.com>, Kees Cook <keescook@...omium.org>, Matthew Wilcox <willy@...radead.org>, Dave Chinner <david@...morbit.com>, James Morris <jmorris@...ei.org>, Michal Hocko <mhocko@...nel.org>, kernel-hardening@...ts.openwall.com, linux-integrity@...r.kernel.org, linux-security-module@...r.kernel.org, igor.stoppa@...wei.com, Dave Hansen <dave.hansen@...ux.intel.com>, Jonathan Corbet <corbet@....net>, Laura Abbott <labbott@...hat.com>, Randy Dunlap <rdunlap@...radead.org>, Mike Rapoport <rppt@...ux.vnet.ibm.com>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 10/17] prmem: documentation Hello, On 25/10/2018 00:04, Mike Rapoport wrote: > I feel that foreword should include a sentence or two saying why we need > the memory protection and when it can/should be used. I was somewhat lost about the actual content of this sort of document. In past reviews of older version of the docs, I go the impression that this should focus more on the use of the API and how to use it. And it seem that different people expect to find here different type of information. What is the best place where to put a more extensive description of the feature? -- igor
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.