linux-kernel - Re: linux-next: build warnings from the build of Linus' tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 11 Oct 2018 13:09:53 +0200
From:   Peter Oberparleiter <oberpar@...ux.ibm.com>
To:     Greg KH <gregkh@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     arnd@...db.de, Masami Hiramatsu <mhiramat@...nel.org>,
        "Steven Rostedt (VMware)" <rostedt@...dmis.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linus <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: build warnings from the build of Linus' tree

On 11.10.2018 12:37, Greg KH wrote:
> On Thu, Oct 11, 2018 at 08:58:49PM +1100, Stephen Rothwell wrote:
>> On Thu, 11 Oct 2018 09:44:36 +0200 Peter Oberparleiter <oberpar@...ux.ibm.com> wrote:
>>> On 11.10.2018 02:48, Stephen Rothwell wrote:
>>>> OK, I have been carrying this "quick fix" patch in linux-next since
>>>> September 7.  Is anyone going to pick this up and send it to
>>>> Greg/Linus, please?  
>>>
>>> Sorry about that - I posted a modified fix at
>>>
>>>   https://lkml.org/lkml/2018/9/13/367
>>>
>>> but didn't get a response. I guess I should have reposted sooner. But
>>> before I do that:
>>>
>>> Arnd: Is this something that you can pick up or should I include someone
>>> else?
>>
>> It would be nice if it could go in before the v4.19 release because the
>> commit that exposed the warnings went into v4.19-rc1.
> 
> I agree.  If someone could at least review/ack it, that would be great.
> What tree does this normally go through?

gcov-kernel related changes are usually picked up by Andrew Morton (on
cc now). In this case I wasn't sure who best to address since its mostly
asm-generic/linker script changes.

-- 
Peter Oberparleiter
Linux on Z Development - IBM Germany