Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Alejandro Hernandez Samaniego <alejandro@enedino.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/3] baremetal-helloworld: Move from skeleton to recipes-extended matching what rust-hello-world is doing
Date: Wed, 11 Jan 2023 16:17:36 +0100	[thread overview]
Message-ID: <Y77TEGpCjI2TGdgI@mail.local> (raw)
In-Reply-To: <20230108191525.1312582-2-alejandro@enedino.org>

Hello,

This fails with:

The following recipes do not have a maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file.
baremetal-helloworld (/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/recipes-extended/baremetal-example/baremetal-helloworld_git.bb)

please run oe-selftest before submitting


On 08/01/2023 12:15:24-0700, Alejandro Hernandez Samaniego wrote:
> Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
> ---
>  .../baremetal-example}/baremetal-helloworld_git.bb                | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename {meta-skeleton/recipes-baremetal/baremetal-examples => meta/recipes-extended/baremetal-example}/baremetal-helloworld_git.bb (100%)
> 
> diff --git a/meta-skeleton/recipes-baremetal/baremetal-examples/baremetal-helloworld_git.bb b/meta/recipes-extended/baremetal-example/baremetal-helloworld_git.bb
> similarity index 100%
> rename from meta-skeleton/recipes-baremetal/baremetal-examples/baremetal-helloworld_git.bb
> rename to meta/recipes-extended/baremetal-example/baremetal-helloworld_git.bb
> -- 
> 2.34.1
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#175637): https://lists.openembedded.org/g/openembedded-core/message/175637
> Mute This Topic: https://lists.openembedded.org/mt/96137379/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-01-11 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08 19:15 [PATCH 1/3] baremetal-helloworld: Enable x86 and x86-64 ports Alejandro Enedino Hernandez Samaniego
2023-01-08 19:15 ` [PATCH 2/3] baremetal-helloworld: Move from skeleton to recipes-extended matching what rust-hello-world is doing Alejandro Enedino Hernandez Samaniego
2023-01-11 15:17   ` Alexandre Belloni [this message]
2023-01-11 15:20     ` [OE-core] " Alejandro Enedino Hernandez Samaniego
2023-01-08 19:15 ` [PATCH 3/3] oe-selftest: Add baremetal toolchain test Alejandro Enedino Hernandez Samaniego
     [not found] ` <17386B65ADE81E78.3916@lists.openembedded.org>
2023-01-08 19:23   ` [OE-core] " Alejandro Enedino Hernandez Samaniego
  -- strict thread matches above, loose matches on Subject: below --
2023-01-12  4:34 [PATCH 2/3] baremetal-helloworld: Move from skeleton to recipes-extended matching what rust-hello-world is doing Alejandro Enedino Hernandez Samaniego
2023-01-12  9:44 ` [OE-core] " Alexandre Belloni
2023-01-12 15:37   ` Alejandro Enedino Hernandez Samaniego

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=Y77TEGpCjI2TGdgI@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=alejandro@enedino.org \
    --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