linux-kernel - Re: linux-next: build failures after merge of the hid 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]

Message-ID: <20200624022740.GA199301@ubuntu-n2-xlarge-x86>
Date:   Tue, 23 Jun 2020 19:27:40 -0700
From:   Nathan Chancellor <natechancellor@...il.com>
To:     Jiri Kosina <jikos@...nel.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Cristian Klein <cristian.klein@...stisys.com>
Subject: Re: linux-next: build failures after merge of the hid tree

Hi Jiri and Cristian,

On Wed, Jun 24, 2020 at 12:13:57AM +0200, Jiri Kosina wrote:
> On Tue, 23 Jun 2020, Stephen Rothwell wrote:
> 
> > > I don't know what caused it, but commit
> > > 
> > >   470376737e88 ("HID: allow building hid.ko as an external module")
> > > 
> > > did not fix it.  BTW, I build with "make O=...".
> 
> That's actually the patch that almost certainly broke it.
> 
> CCing Cristian (author of that patch) and Nathan, who apparently sent a 
> fixup patch for this, but I haven't seen it, as our corporate mailserver 
> had severe issues yesterday.
> 
> If there is no resolution by tomorrow, we'll just drop it.
> 
> -- 
> Jiri Kosina
> SUSE Labs
> 

Sorry, I was not clear in my message about what I was "fixing", which
was the fact that Cristian's initial reply was top posted, which I moved
to the bottom. I thought that would have been apparent in a mail client,
my bad :( I have not sent a fix for this issue.

Cheers,
Nathan