From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: michael.opdenacker@rootcommit.com,
yocto-patches@lists.yoctoproject.org,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [yocto-patches] [PATCH meta-rockchip] orangepi-3b: add
Date: Thu, 20 Nov 2025 16:54:41 +0000 (UTC) [thread overview]
Message-ID: <ae649aeb-d73d-4d51-8f69-cc6a2c2633fb@rootcommit.com> (raw)
In-Reply-To: <20251120-petite-copper-chupacabra-c70e6e@lemur>
Hi Konstantin
On 11/20/25 17:38, Konstantin Ryabitsev wrote:
> On Thu, Nov 20, 2025 at 11:40:05AM +0100, Quentin Schulz wrote:
>> On 11/20/25 11:34 AM, Michael Opdenacker via lists.yoctoproject.org wrote:
>>> Oops, it seems b4 messed up the subject line.
>>> It should contain "[meta-rockchip][PATCH]"
>>>
>> All my patches sent by b4 have the same pattern as yours. Glancing at b4's
>> code, I believe this is how it's intended to work, c.f.
>> get_rebuilt_subject() in src/b4/__init__.py
> I just accepted some patches into current master that should deal with
> [presubject] the way Yocto lists expect that to happen. Please try them out if
> you can.
Do you mean meta-rockchip? I believe I have the latest changes and I'm
using Quentin's .b4-config file from last year...
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next prev parent reply other threads:[~2025-11-20 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1879B0158049C4B6.1423420@lists.yoctoproject.org>
2025-11-20 10:34 ` [yocto-patches] [PATCH meta-rockchip] orangepi-3b: add Michael Opdenacker
2025-11-20 10:40 ` Quentin Schulz
2025-11-20 11:03 ` Michael Opdenacker
2025-11-20 16:38 ` Konstantin Ryabitsev
2025-11-20 16:54 ` Michael Opdenacker [this message]
2025-11-20 17:04 ` Quentin Schulz
2025-11-20 10:25 Michael Opdenacker
2025-11-20 10:35 ` [yocto-patches] " Quentin Schulz
2025-11-20 11:57 ` Michael Opdenacker
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=ae649aeb-d73d-4d51-8f69-cc6a2c2633fb@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=konstantin@linuxfoundation.org \
--cc=quentin.schulz@cherry.de \
--cc=yocto-patches@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.