From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME}
Date: Mon, 12 Jun 2023 18:17:29 +0200 [thread overview]
Message-ID: <20230612161729256e0cc6@mail.local> (raw)
In-Reply-To: <CA+chaQdAaZ9mc_jfvL+5VJkGoybs0FrhVuTpGS9dRu2hxikCmQ@mail.gmail.com>
Hello,
On 12/06/2023 17:35:30+0200, Martin Jansa wrote:
> On Sat, May 27, 2023 at 7:21 AM Martin Jansa via lists.openembedded.org
> <Martin.Jansa=gmail.com@lists.openembedded.org> wrote:
>
> > On Fri, May 26, 2023 at 8:09 PM Alexandre Belloni <
> > alexandre.belloni@bootlin.com> wrote:
> >
> >> Hello,
> >>
> >> The series causes oe-selftest failures:
> >>
> >>
> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5254/steps/14/logs/stdio
> >>
> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/1468/steps/14/logs/stdio
> >>
> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5225/steps/14/logs/stdio
> >>
> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/5175/steps/14/logs/stdio
> >>
> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5217/steps/14/logs/stdio
> >
> >
> > Hi,
> >
> > I was able to reproduce it locally and it's caused by newer test (which
> > wasn't merged yet last time I've run selftest with these changes):
> >
> > https://git.openembedded.org/openembedded-core/commit/?id=06af6795cf6f079362303bddb39a14459e228e72
> > which hardcodes the expected image name, I'll send fix for this shortly.
> >
>
> Hi, I see that the selftest fix was already merged to master and this
> change was in abelloni/master-next-success for a while, but now it's
> dropped (and it's not in master nor master-next).
>
> Should I resend the series again or what's the process now?
It would be great if you could rebase your series. I dropped your patch
because it conflicted. I had on my TODO list to solve those conflicts
but if you do, it makes my life easier ;)
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-06-12 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:22 [PATCH 1/2] image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME} Martin Jansa
2023-05-25 10:22 ` [PATCH 2/2] kernel-devicetree: install dtb files without -${KERNEL_DTB_NAME} suffix Martin Jansa
2023-05-26 18:09 ` [OE-core] [PATCH 1/2] image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME} Alexandre Belloni
2023-05-27 5:21 ` Martin Jansa
2023-05-27 5:49 ` [PATCH] selftest: wic.py respect IMAGE_LINK_NAME Martin Jansa
[not found] ` <1762E887A919FB5A.6918@lists.openembedded.org>
2023-06-12 15:35 ` [OE-core] [PATCH 1/2] image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME} Martin Jansa
2023-06-12 16:17 ` Alexandre Belloni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230612161729256e0cc6@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox