On 14 May 2013 23:49, Kevin Hilman wrote:
> Fathi Boudra writes:
>
> [...]
>
>>> Is there a way for us (linaro folks) to see more of the Jenkins setup
>>> for these jobs (including the scripts.) There appears to be some useful
>>> add-ons being used. Read-only access to the detailed configuratio
Not trying to hijack this thread, but I studied in my security class that
SHA1 is being attacked so to speak in terms of crypto analysis and it was
suggested in the book that it not be used but something like SHA512 be used
instead.
Just to give you all a heads up :)
On Tue, May 14, 2013 at 6:49
+++ Kevin Hilman [2013-05-14 11:52 -0700]:
> Nicolas Dechesne writes:
>
> > On Thu, May 9, 2013 at 7:56 PM, Fathi Boudra wrote:
> >
> >> > Hi all,
> >> >
> >> > I just wanted to forward this thread from LAKML to linaro-dev:
> >> > http://article.gmane.org/gmane.linux.ports.tegra/10683
> >> >
> >>
Fathi Boudra writes:
[...]
>> Is there a way for us (linaro folks) to see more of the Jenkins setup
>> for these jobs (including the scripts.) There appears to be some useful
>> add-ons being used. Read-only access to the detailed configuration of
>> the jenkins jobs would be very useful.
>
> Y
On 14 May 2013 21:52, Kevin Hilman wrote:
> I'll second Nicolas' comments.
>
> As a kernel developer and upstream maintainer (and now working for
> Linaro), it's not at all clear (or documented that I can find) how
> kernel CI is being structure and implemented nor how it could be useful
> for ker
On 05/08/2013 10:53 PM, Andrey Konovalov wrote:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
The 13.05 linux-linaro release will be v3.10-rc2 based,
May 13: v3.10-rc1 based linux-linaro-core-tracking (llct) rebuild
Done: the tag is llct-20130514.0
Changes:
Nicolas Dechesne writes:
> On Thu, May 9, 2013 at 7:56 PM, Fathi Boudra wrote:
>
>> > Hi all,
>> >
>> > I just wanted to forward this thread from LAKML to linaro-dev:
>> > http://article.gmane.org/gmane.linux.ports.tegra/10683
>> >
>> > Seems there is lots desire for an improvement to automated b
On Tue, 2013-05-14 at 14:16 +0200, Ard Biesheuvel wrote:
> These assembler implementations of SHA1 and AES have been
> in the upstream source tree since September 2012 but need
> to be selected explicitly in order to be enabled.
>
> Signed-off-by: Ard Biesheuvel
> ---
> linaro/configs/linaro-bas
These assembler implementations of SHA1 and AES have been
in the upstream source tree since September 2012 but need
to be selected explicitly in order to be enabled.
Signed-off-by: Ard Biesheuvel
---
linaro/configs/linaro-base.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/linaro/con
