On 01/30/2017 02:15 PM, Stefan Weil wrote:
> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>
> Signed-off-by: Stefan Weil
> ---
>
> v2: Re-sent as v1 was damaged by my mailer.
>
> This is also broken in Debian.
>
> In addition, there is no default
On 22.03.2017 10:07, Christian Borntraeger wrote:
> On 01/30/2017 02:15 PM, Stefan Weil wrote:
>> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>>
>> Signed-off-by: Stefan Weil
>> ---
>>
>> v2: Re-sent as v1 was damaged by my mailer.
>>
>> This is
On 01/30/2017 02:15 PM, Stefan Weil wrote:
> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>
> Signed-off-by: Stefan Weil
> ---
>
> v2: Re-sent as v1 was damaged by my mailer.
>
> This is also broken in Debian.
>
> In addition, there is no default
On 16.03.2017 15:46, Philippe Mathieu-Daudé wrote:
> Hi Stefan, Richard.
>
> On 03/16/2017 10:28 AM, David Hildenbrand wrote:
>> On 02.03.2017 20:56, David Hildenbrand wrote:
>>> Am 30.01.2017 um 14:15 schrieb Stefan Weil:
Returning NULL from get_max_cpu_model results in a SIGSEGV runtime
Hi Stefan, Richard.
On 03/16/2017 10:28 AM, David Hildenbrand wrote:
On 02.03.2017 20:56, David Hildenbrand wrote:
Am 30.01.2017 um 14:15 schrieb Stefan Weil:
Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
Signed-off-by: Stefan Weil
---
v2:
On 02.03.2017 20:56, David Hildenbrand wrote:
> Am 30.01.2017 um 14:15 schrieb Stefan Weil:
>> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>>
>> Signed-off-by: Stefan Weil
>> ---
>>
>> v2: Re-sent as v1 was damaged by my mailer.
>>
>> This is also
Am 30.01.2017 um 14:15 schrieb Stefan Weil:
> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>
> Signed-off-by: Stefan Weil
> ---
>
> v2: Re-sent as v1 was damaged by my mailer.
>
> This is also broken in Debian.
>
> In addition, there is no
Am 30.01.2017 um 14:15 schrieb Stefan Weil:
> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>
> Signed-off-by: Stefan Weil
> ---
>
> v2: Re-sent as v1 was damaged by my mailer.
>
Just tested your patch:
Reviewed-by: David Hildenbrand
On 30 January 2017 at 14:10, David Hildenbrand wrote:
> Am 30.01.2017 um 14:15 schrieb Stefan Weil:
>> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>>
>> Signed-off-by: Stefan Weil
>> ---
>>
>> v2: Re-sent as v1 was damaged by my
Am 30.01.2017 um 14:15 schrieb Stefan Weil:
> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>
> Signed-off-by: Stefan Weil
> ---
>
> v2: Re-sent as v1 was damaged by my mailer.
>
> This is also broken in Debian.
>
> In addition, there is no
Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
Signed-off-by: Stefan Weil
---
v2: Re-sent as v1 was damaged by my mailer.
This is also broken in Debian.
In addition, there is no default CPU ("any"), so binfmt and related
actions currently don't
11 matches
Mail list logo