On 14.07.2018 18:29, m...@netbsd.org wrote:
> On Sat, Jul 14, 2018 at 03:09:41PM +, Maxime Villard wrote:
>> Module Name: src
>> Committed By:maxv
>> Date:Sat Jul 14 15:09:41 UTC 2018
>>
>> Modified Files:
>> src/sys/arch/bebox/conf: INSTALL
>> src/sys/arch/evb
In article <20180715143050.ga28...@britannica.bec.de>,
Joerg Sonnenberger wrote:
>On Sat, Jul 14, 2018 at 08:36:13PM -0400, Christos Zoulas wrote:
>> Module Name: src
>> Committed By:christos
>> Date:Sun Jul 15 00:36:13 UTC 2018
>>
>> Modified Files:
>> src/sys/arch/
In article <20180715143153.gb28...@britannica.bec.de>,
Joerg Sonnenberger wrote:
>On Sat, Jul 14, 2018 at 07:41:43PM -0400, Christos Zoulas wrote:
>> Module Name: src
>> Committed By:christos
>> Date:Sat Jul 14 23:41:43 UTC 2018
>>
>> Modified Files:
>> src/external/
On Sat, Jul 14, 2018 at 08:36:13PM -0400, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Sun Jul 15 00:36:13 UTC 2018
>
> Modified Files:
> src/sys/arch/arm/include: int_fmtio.h
>
> Log Message:
> Fix formats for gcc where int64 is long not long long (li
On Sat, Jul 14, 2018 at 07:41:43PM -0400, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Sat Jul 14 23:41:43 UTC 2018
>
> Modified Files:
> src/external/gpl3/gcc/dist/libiberty: alloca.c
>
> Log Message:
> clang does not like auto in c++
This is not abo
On Sun, 15 Jul 2018, Paul Goyette wrote:
Any chance that this will fix kern/52919?
If not, can we do some additional re-arrangement of struct cpu_info to
address the problem?
And in any case, shouldn't this cause a bump in kernel version, since
you've changed a structure that is shared b
Any chance that this will fix kern/52919?
If not, can we do some additional re-arrangement of struct cpu_info to
address the problem?
On Sun, 15 Jul 2018, Maxime Villard wrote:
Module Name:src
Committed By: maxv
Date: Sun Jul 15 08:47:43 UTC 2018
Modified Files:
sr
