Am Montag, 5. März 2018, 11:41:42 CEST schrieb anton.iva...@cambridgegreys.com:
> From: Anton Ivanov
>
> The patches for the UML vector drivers were in-flight when
> the timer changes happened and were not covered by them.
>
> This change migrates vector_kern.c to use the new timer API.
>
> Sig
Am Montag, 5. März 2018, 14:29:05 CEST schrieb anton.iva...@cambridgegreys.com:
> From: Anton Ivanov
>
> Vector RAW in UML needs to BPF filter its own MAC only
> if QDISC_BYPASS has failed. If QDISC_BYPASS is successful, the
> frames originated locally are not visible to readers on the
> raw sock
On Wed, Mar 28, 2018 at 11:04 PM, Geert Uytterhoeven
wrote:
> On Thu, Mar 29, 2018 at 12:35 AM, Richard Weinberger wrote:
>> Am Donnerstag, 29. März 2018, 00:19:39 CEST schrieb Joel Fernandes:
>>> On Wed, Mar 28, 2018 at 6:19 AM, Richard Weinberger wrote:
>>> > Am Mittwoch, 28. März 2018, 15:11:
Am Donnerstag, 29. März 2018, 22:20:47 CEST schrieb Joel Fernandes:
> Thanks a lot! I am wondering why the same compiler works when running
> the test for a regular image. Maybe different compiler flags. Anyway
> good to learn this.
>
> Also one more slightly OT question, why is UML only doing UP
Yes,
Next version though, I have some tweaks enqueued for the socket initialization.
We can combine them with these.
On 29 March 2018 20:51:55 BST, SF Markus Elfring
wrote:
>> Date: Sun, 11 Mar 2018 16:06:16 +0100
>>
>> Some update suggestions were taken into account
>> from static source co
While the function will never returns, gcc will warns.
Add a return statement to make gcc happy.
Before f44f1e7da7c8 we never noticed because gcc knows that longjmp does
not return.
arch/um/os-Linux/skas/process.c: In function ‘start_idle_thread’:
arch/um/os-Linux/skas/process.c:613:1: warning: co
