public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: "Michael Opdenacker" <michael.opdenacker@bootlin.com>,
	"Jörg Sommer" <joerg.sommer@navimatix.de>
Subject: [kirkstone][PATCH 8/9] kernel-dev: join mkdir commands with -p
Date: Sun, 14 Apr 2024 20:20:10 +0200	[thread overview]
Message-ID: <20240414182011.994356-9-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240414182011.994356-1-michael.opdenacker@bootlin.com>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

From: Jörg Sommer <joerg.sommer@navimatix.de>

To make it more obvious which directories are needed, pass only these to
*mkdir* and use the option `-p` to create the missing parents.

Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
 documentation/kernel-dev/common.rst | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst
index cbcb30281a..3f9d8d48e4 100644
--- a/documentation/kernel-dev/common.rst
+++ b/documentation/kernel-dev/common.rst
@@ -383,11 +383,7 @@ home directory:
 
 1. *Create Structure*: Create the layer's structure::
 
-      $ mkdir meta-mylayer
-      $ mkdir meta-mylayer/conf
-      $ mkdir meta-mylayer/recipes-kernel
-      $ mkdir meta-mylayer/recipes-kernel/linux
-      $ mkdir meta-mylayer/recipes-kernel/linux/linux-yocto
+      $ mkdir -p meta-mylayer/conf meta-mylayer/recipes-kernel/linux/linux-yocto
 
    The ``conf`` directory holds your configuration files, while the
    ``recipes-kernel`` directory holds your append file and eventual
@@ -1044,9 +1040,7 @@ Section.
    additional structure to your layer using the following commands::
 
       $ cd ~/meta-mylayer
-      $ mkdir recipes-kernel
-      $ mkdir recipes-kernel/linux
-      $ mkdir recipes-kernel/linux/linux-yocto
+      $ mkdir -p recipes-kernel recipes-kernel/linux/linux-yocto
 
    Once you have created this
    hierarchy in your layer, you can move the patch file using the
-- 
2.34.1



  parent reply	other threads:[~2024-04-14 18:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 18:20 [kirkstone][PATCH 0/9] documentation backports michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 1/9] release-notes-4.0.17: reorder CVEs michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 2/9] docs: conf.py: properly escape backslashes for latex_elements michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 3/9] manuals: refer to new yocto-patches mailing list wherever appropriate michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 4/9] manuals: fix duplicate "stylecheck" target michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 5/9] manuals: add initial sphinx-lint support michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 6/9] manuals: fix trailing spaces michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 7/9] manuals: fix incorrect double backticks michael.opdenacker
2024-04-14 18:20 ` michael.opdenacker [this message]
2024-04-14 18:20 ` [kirkstone][PATCH 9/9] manuals: remove tab characters 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=20240414182011.994356-9-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=joerg.sommer@navimatix.de \
    /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