From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Frederic Martinsons <frederic.martinsons@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: openembedded-core@lists.openembedded.org, alex.kiernan@gmail.com
Subject: Re: [OE-core] [PATCH V4 5/5] meta-selftest: provide a recipe for zvariant
Date: Thu, 30 Mar 2023 12:35:23 +0100 [thread overview]
Message-ID: <d83c8058e83e33d02e4650c2d29c1a03a6db739f.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+cAker5pJUBoOSEVZtk++394xGgXqcDDD9eFJpu07+Ai5PaWg@mail.gmail.com>
On Thu, 2023-03-30 at 11:47 +0200, Frederic Martinsons wrote:
> What version of bitbake you had pulled ?
> Because "mandatory checksum on crates" is a patch I submitted two
> weeks ago
> (https://patchwork.yoctoproject.org/project/bitbake/patch/20230317081
> 916.1857201-2-frederic.martinsons@gmail.com/))
> and it is not yet merged in bitbake master nor in poky master.
>
> So I construct the present series without these patches in mind since
> it is not related.
> I you plan to merge the previous series, I can update the zvariant
> for this recipe of course
> it can be done by issuing "bitbake -c update_crates zvariant" if this
> patch
> (https://patchwork.yoctoproject.org/project/bitbake/patch/20230316121
> 249.28209-1-frederic.martinsons@gmail.com/) is present
>
> I'm sorry, I must admit that I'm kinda lost with the patch submission
> process when it impacts multiple different
> projects.
> Can you advise on the way of doing this?
I've merged the other series now so could you rebase this one on master
please?
Usually if there are two related series you'd base one on the other and
note it in the 0/X of the series. We'd work on the assumption the
earlier patches would merge first.
The holdup was that I wanted to check something in the bitbake patch,
which turned out to be fine, I just needed to do it as part of review
due diligence.
Cheers,
Richard
next prev parent reply other threads:[~2023-03-30 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 15:30 [PATCH V4 0/5] Extend cargo based recipe support frederic.martinsons
2023-03-29 15:30 ` [PATCH V4 1/5] cargo_common.bbclass: Support local github repos frederic.martinsons
2023-03-29 15:30 ` [PATCH V4 2/5] cargo_common.bbclass: add support of user in url for patch frederic.martinsons
2023-03-29 15:30 ` [PATCH V4 3/5] devtool: add support for multiple git url inside a cargo based recipe frederic.martinsons
2023-03-29 15:30 ` [PATCH V4 4/5] patch: support of git patches when the source uri contained subpath parameter frederic.martinsons
2023-03-29 15:30 ` [PATCH V4 5/5] meta-selftest: provide a recipe for zvariant frederic.martinsons
2023-03-30 9:03 ` [OE-core] " Alexandre Belloni
2023-03-30 9:14 ` Alexandre Belloni
2023-03-30 9:47 ` Frédéric Martinsons
2023-03-30 11:35 ` Richard Purdie [this message]
2023-03-30 12:25 ` Frédéric Martinsons
[not found] ` <1751320CE5466FC4.12651@lists.openembedded.org>
2023-03-30 12:48 ` Frédéric Martinsons
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=d83c8058e83e33d02e4650c2d29c1a03a6db739f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kiernan@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=frederic.martinsons@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