I once again have to stress that 'devtool upgrade' rebases the patches
automatically. Please do use it, it works for the vast majority of
oe-core items.

Alex

On Wed, 21 Sept 2022 at 19:14, Markus Volk <f_...@t-online.de> wrote:
>
> I started with a clean master branch and encountered the patch fuzz warning 
> on the first build. But to verify that the driver was working, I wanted to 
> run my wayland image with 'runqemu'. That required a whole bunch of extra 
> files to be changed, and I ended up forgetting to fix the patch. Sorry
>
> But I can confirm that I was able to run the image with the runqemu script. 
> The driver should work.
>
> Am Mi, 21. Sep 2022 um 14:38:02 +0100 schrieb Richard Purdie 
> <richard.pur...@linuxfoundation.org>:
>
> On Wed, 2022-09-21 at 09:51 +0200, Markus Volk wrote:
>
> Signed-off-by: Markus Volk <f_...@t-online.de> --- 
> .../virglrenderer/virglrenderer_0.10.3.bb | 33 +++++++++++++++++++ 
> .../virglrenderer/virglrenderer_0.9.1.bb | 25 -------------- 2 files changed, 
> 33 insertions(+), 25 deletions(-) create mode 100644 
> meta/recipes-graphics/virglrenderer/virglrenderer_0.10.3.bb delete mode 
> 100644 meta/recipes-graphics/virglrenderer/virglrenderer_0.9.1.bb
>
> The patches weren't refreshed leading to fuzz warnings: 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5884/steps/11/logs/warnings
>  
> https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/5931/steps/11/logs/warnings
>  and many many more like it in that build. How was this tested? :/ Cheers, 
> Richard
>
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170964): 
https://lists.openembedded.org/g/openembedded-core/message/170964
Mute This Topic: https://lists.openembedded.org/mt/93821898/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to