All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org, Quentin Schulz <foss@0leil.net>
Subject: Re: [docs] [PATCH] ref-manual: remove unused example recipe source files
Date: Tue, 27 Jul 2021 14:36:10 +0200	[thread overview]
Message-ID: <dc7f8298-bf2c-1466-1734-882a192c82d8@bootlin.com> (raw)
In-Reply-To: <4c34e5320bb80e9234ca68c1e110e0581853766e.camel@linuxfoundation.org>

Richard, Quentin,

Many thanks for your feedback.

On 7/27/21 1:38 PM, Richard Purdie wrote:
> On Tue, 2021-07-27 at 13:23 +0200, Quentin Schulz wrote:
>> I wouldn't remove them as I find example recipes to be very welcomed as
>> real life examples of what can/needs to be done. It shows also some
>> gotchas and what a minimal recipe should look like.
>>
>> What I have to complain about those files currently is that they are not
>> built and they weren't working for a while, which is a bit of a shame
>> for example recipes :)
>>
>> I don't think keeping them in the yocto-docs is something we want to
>> push for (at least I won't), but I feel like we should keep them
>> somewhere they are built so we maintain them along other recipes.
>>
>> I can see that we have a recipe for an out-of-tree kernel drievr recipe
>> available in poky/meta-skeleton layer (called hello-mod). I guess this
>> is a place we could put the examples you want to remove from yocto-docs?
> If they were in meta-skeleton we could build/test them...


Thanks for the suggestion! I'll propose a patch doing this.

Cheers,

Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2021-07-27 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16959EEB5BD85597.12821@lists.yoctoproject.org>
2021-07-27 10:29 ` [docs] [PATCH] ref-manual: remove unused example recipe source files Michael Opdenacker
2021-07-27 11:23   ` Quentin Schulz
2021-07-27 11:38     ` Richard Purdie
2021-07-27 12:36       ` Michael Opdenacker [this message]
     [not found]       ` <1695A60376DC3ECA.18160@lists.yoctoproject.org>
2021-07-28 13:56         ` Michael Opdenacker
2021-07-29 13:48           ` Richard Purdie
2021-07-30 16:41             ` Michael Opdenacker
     [not found]             ` <16969F1E09D6E656.27324@lists.yoctoproject.org>
2021-08-02 16:16               ` Michael Opdenacker
     [not found]         ` <1695F8F487052006.29235@lists.yoctoproject.org>
2021-07-29 13:39           ` 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=dc7f8298-bf2c-1466-1734-882a192c82d8@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=richard.purdie@linuxfoundation.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.