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  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, 4 Jul 2019 10:53:26 -0500
From:   Nishanth Menon <nm@...com>
To:     Felipe Balbi <balbi@...nel.org>
CC:     Pawel Laszczak <pawell@...ence.com>, Greg KH <greg@...ah.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        Roger Quadros <rogerq@...com>
Subject: Re: linux-next: build failure after merge of the usb and usb-gadget
 trees

On 11:25-20190704, Felipe Balbi wrote:
[...]

> This is what I get for trusting people to do their part. I couldn't even
> compile test this since I don't have ARM compilers anymore (actually,
> just installed to test). Your customer, however, uses ARM cores so I
> would expect you to have at least compile tested this on ARM. How come
> this wasn't verified by anybody at TI?

Sorry about that Felipe/Greg, will try and make sure we put in steps so
that this does'nt happen again.

> 
> TI used to have automated testing for many of the important defconfigs,
> is that completely gone? Are you guys relying entirely on linux-next?

We still do. Kind of a unfortunately co-incidence, there has been for a
few weeks a downtime given the test infrastructure has been changing and
the continual automated testing env is down for community kernel. But,
that said, we also did move to focussing on linux-next, which should be
revisited.


-- 
Regards,
Nishanth Menon

Powered by blists - more mailing lists