public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [docs] [PATCH 4/4] ref-manual: classes: kernel: document automatic defconfig usage
Date: Tue, 9 May 2023 14:45:12 +0200	[thread overview]
Message-ID: <cf5bb128-94cf-b66d-ca14-40844d7c1196@bootlin.com> (raw)
In-Reply-To: <175D7A12A151A6F9.26836@lists.yoctoproject.org>


On 09.05.23 at 14:40, Michael Opdenacker via lists.yoctoproject.org wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> From: Luca Ceresoli <luca.ceresoli@bootlin.com>
>
> Since a very long time the kernel bbclass uses a defconfig file from
> SRC_URI automatically. Document this feature.
>
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
>   documentation/ref-manual/classes.rst | 7 +++++++
>   1 file changed, 7 insertions(+)


These last two changes are for Mickledore too (I've just fixed their title).
Michael.

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



      parent reply	other threads:[~2023-05-09 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 12:40 [PATCH 1/4] [mickledore] migration-guides: release-notes-4.2: add doc improvement highlights michael.opdenacker
2023-05-09 12:40 ` [PATCH 2/4] [mickledore] release-notes-4.2: update known issues and Repositories/Downloads michael.opdenacker
2023-05-09 12:40 ` [PATCH 3/4] ref-manual: classes: kernel: remove incorrect sentence opening michael.opdenacker
2023-05-09 12:40 ` [PATCH 4/4] ref-manual: classes: kernel: document automatic defconfig usage michael.opdenacker
     [not found] ` <175D7A12A151A6F9.26836@lists.yoctoproject.org>
2023-05-09 12:45   ` Michael Opdenacker [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=cf5bb128-94cf-b66d-ca14-40844d7c1196@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=luca.ceresoli@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