[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7cfb5d06-96a6-41a0-9f57-d9df1204f45e@gmail.com>
Date: Sat, 16 Feb 2019 17:15:38 +0200
From: Igor Stoppa <igor.stoppa@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Igor Stoppa <igor.stoppa@...wei.com>,
Andy Lutomirski <luto@...capital.net>, Nadav Amit <nadav.amit@...il.com>,
Matthew Wilcox <willy@...radead.org>, Kees Cook <keescook@...omium.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Thiago Jung Bauermann <bauerman@...ux.ibm.com>,
Ahmed Soliman <ahmedsoliman@...a.vt.edu>, linux-integrity@...r.kernel.org,
kernel-hardening@...ts.openwall.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v5 03/12] __wr_after_init: Core and default arch
On 15/02/2019 10:57, Peter Zijlstra wrote:
> Where are the comments and Changelog notes ? How is an arch maintainer
> to be aware of this requirement when adding support for his/her arch?
Yes, it will be fixed in the next revision. I've added comment to the
core wr_assign function and also to the changelogs for the patches
enabling it on x86_64 and arm64, respectively.
Should I add mention of it also in the documentation?
--
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.
