Re: [OE-core] [RFC][PATCH 0/5] Kernel artifacts naming changes

On Mon, Jul 2, 2018 at 11:16 AM, Martin Jansa wrote: > Any comment about this RFC? > > Should I send rebased version? Yes, please. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854

Re: [OE-core] [RFC][PATCH 0/5] Kernel artifacts naming changes

Any comment about this RFC? Should I send rebased version? On Tue, Nov 21, 2017 at 12:58 PM Otavio Salvador < otavio.salva...@ossystems.com.br> wrote: > Hello Martin, > > On Mon, Nov 20, 2017 at 6:11 PM, Martin Jansa > wrote: > ... > > This RFC doesn't implement it all, but it makes naming all

Re: [OE-core] [RFC][PATCH 0/5] Kernel artifacts naming changes

Hello Martin, On Mon, Nov 20, 2017 at 6:11 PM, Martin Jansa wrote: ... > This RFC doesn't implement it all, but it makes naming all the artifacts in > consistent way a bit easier. If there is an agreement that OE should support > the naming scenario described above, I'll

[OE-core] [RFC][PATCH 0/5] Kernel artifacts naming changes

This is only RFC, because it wasn't tested in all possible combinations people might use. I did some limited testing with raspberrypi3 and raspberrypi3-64 with default configuration and also our modified naming where rpi builds were failing and we had to use our own sdcard_image-rpi.bbclass to