Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mvcfp111.fsf@concordia.ellerman.id.au>
Date: Tue, 21 Mar 2017 18:00:26 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Kees Cook <keescook@...omium.org>, Jonathan Corbet <corbet@....net>, Andrew Donnellan <andrew.donnellan@....ibm.com>
Cc: Emese Revfy <re.emese@...il.com>, "kernel-hardening\@lists.openwall.com" <kernel-hardening@...ts.openwall.com>, "linux-doc\@vger.kernel.org" <linux-doc@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, "linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: Re: [PATCH] gcc-plugins: update architecture list in documentation

Kees Cook <keescook@...omium.org> writes:

> On Mon, Mar 20, 2017 at 1:39 AM, Michael Ellerman <mpe@...erman.id.au> wrote:
>> Andrew Donnellan <andrew.donnellan@....ibm.com> writes:
>>
>>> Commit 65c059bcaa73 ("powerpc: Enable support for GCC plugins") enabled GCC
>>> plugins on powerpc, but neglected to update the architecture list in the
>>> docs. Rectify this.
>>>
>>> Fixes: 65c059bcaa73 ("powerpc: Enable support for GCC plugins")
>>> Signed-off-by: Andrew Donnellan <andrew.donnellan@....ibm.com>
>>> ---
>>>  Documentation/gcc-plugins.txt | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> It would be nice to merge this for v4.11, so the docs are up to do date
>> with the code for the release.
>>
>> I'm not sure who owns it though, should it go via Jon as docs
>> maintainer (added to CC), or via Kees tree or mine?
>
> If you have other changes queued for v4.11, please take it via your
> tree. Otherwise, perhaps the docs tree or mine? (I don't currently
> have any fixes queued; I'm just trying to minimize pull requests going
> to Linus...)

I have some fixes queued already, so unless Jon yells I'll take it in
the next day or so.

cheers

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.