From: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Cc: thomas.petazzoni@bootlin.com, Khem Raj <raj.khem@gmail.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH v2 0/2] Move RISC-V recipe-specific configuration out of common includes
Date: Wed, 14 Jan 2026 13:34:12 +0100 [thread overview]
Message-ID: <0b148d6c-561a-4fc1-b42c-fc645fd4e526@bootlin.com> (raw)
In-Reply-To: <05138af86479c4310bb28a8a4077c80a5607b0a9.camel@linuxfoundation.org>
Hello,
On 1/14/26 13:30, Richard Purdie wrote:
> On Wed, 2026-01-14 at 11:01 +0100, Joao Marcos Costa via lists.openembedded.org wrote:
>> Hello,
>>
>> Gentle ping!
>>
>> On 1/7/26 16:14, João Marcos Costa wrote:
>>> This series moves RISC-V specific configuration out of linux-
>>> yocto.inc into a
>>> new inc file: linux-yocto-features.inc.
>>>
>>> By relocating these RISC-V specific settings, the configuration
>>> remains
>>> available for oe-core builds while avoiding unintended side effects
>>> for external
>>> or custom recipes that require such include file.
>>>
>>> The first patch only changes u-boot, and u-boot contains only one
>>> versioned
>>> recipe, so I kept it as it was in v1.
>>>
>>> Changes in v2:
>>> - As per the comments in v1, I created a new inc file that is now
>>> included in
>>> the versioned recipes
>>>
>>
>> Would you have any thoughts on this v2? Thanks.
>
> See the weekly status reports. We are having huge problems merging
> patches at the moment due to failures in our testing infrastructure.
Yes, I just read them.
> Patches which fix some of those issues get priority, most other things
> are delayed, sorry. Time we might have spent on patch review is also
> needed elsewhere right now.
>
> I wish I had something better to report :/.
>
> Cheers,
>
> Richard
I completely understand, no worries. Thanks for the reply.
--
Best regards,
João Marcos Costa
prev parent reply other threads:[~2026-01-14 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 15:14 [PATCH v2 0/2] Move RISC-V recipe-specific configuration out of common includes João Marcos Costa
2026-01-07 15:14 ` [PATCH v2 1/2] u-boot: relocate SRC_URI_RISCV into recipe João Marcos Costa
2026-01-07 15:14 ` [PATCH v2 2/2] linux-yocto: relocate KERNEL_FEATURES_RISCV João Marcos Costa
2026-02-10 9:05 ` Joao Marcos Costa
2026-01-14 10:01 ` [PATCH v2 0/2] Move RISC-V recipe-specific configuration out of common includes Joao Marcos Costa
2026-01-14 12:30 ` [OE-core] " Richard Purdie
2026-01-14 12:34 ` Joao Marcos Costa [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=0b148d6c-561a-4fc1-b42c-fc645fd4e526@bootlin.com \
--to=joaomarcos.costa@bootlin.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.com \
/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