From: Alexander Dahl <ada@thorsis.com>
To: Markus Heidelberg <m.heidelberg@cab.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] Fix typos "can/must be uses" -> "used"
Date: Tue, 9 Apr 2024 10:45:00 +0200 [thread overview]
Message-ID: <20240409-patchwork-balmy-42af6b4a5962@thorsis.com> (raw)
In-Reply-To: <20240409073745.1549906-2-m.heidelberg@cab.de>
Hello Markus,
Am Tue, Apr 09, 2024 at 09:37:44AM +0200 schrieb Markus Heidelberg:
> Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> ---
> doc/multi_image_platforms.inc | 6 +++---
> doc/ref_make_variables.rst | 6 +++---
> rules/other/Toplevel.make | 2 +-
> 3 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/doc/multi_image_platforms.inc b/doc/multi_image_platforms.inc
> index 2c8838f4e..726a42767 100644
> --- a/doc/multi_image_platforms.inc
> +++ b/doc/multi_image_platforms.inc
> @@ -26,7 +26,7 @@ package rules manually. See :ref:`adding_new_packages` for more details one
> how to create a new package.
>
> .. note:: PTXdist looks in ``patches/$(<PKG>)`` for the patches. Symlinks
> - can be uses to share the patch stack across multiple bootloader packages.
> + can be used to share the patch stack across multiple bootloader packages.
>
> .. _multi_image_individual_root_filesystems:
>
> @@ -46,7 +46,7 @@ There are two ways to mange the package list for the image:
> Manually create the package list by listing package names or using **make**
> macros to manipulate the default package list ``$(PTX_PACKAGES_INSTALL)``.
>
> - To add a single custom package, extra packages can be uses. An extra package
> + To add a single custom package, extra packages can be used. An extra package
> is not added to ``$(PTX_PACKAGES_INSTALL)``. It is created by modifying the
> package rule like this:
>
> @@ -93,7 +93,7 @@ The final steps are highly hardware dependent. In some cases a bootloader
> image and a rootfs are all that is needed.
>
> To boot from SD-Card a disk image including bootloader, partition table and
> -rootfs is needed. The ``image-genimage`` template can be uses again to
> +rootfs is needed. The ``image-genimage`` template can be used again to
> create such an image for each variant.
>
> .. note:: The genimage config files in ``config/images/`` are good examples
> diff --git a/doc/ref_make_variables.rst b/doc/ref_make_variables.rst
> index 31616ac6f..6bba9db5d 100644
> --- a/doc/ref_make_variables.rst
> +++ b/doc/ref_make_variables.rst
> @@ -478,7 +478,7 @@ different.
> package then this package should be selected in the menu file.
>
> ``<PKG>_PKGS``
> - This is another mechanism to add files to the image. It can be uses
> + This is another mechanism to add files to the image. It can be used
> instead of or in addition to ``<PKG>_FILES``. It must be set to a list of
> ptxdist packages (the lowercase name of the packages). PTXdist will add
> the necessary dependencies.
> @@ -486,9 +486,9 @@ different.
> Note that this will not ensure that the packages are enabled or that all
> all package dependencies are satisfied. ``$(PTX_PACKAGES_INSTALL)`` can
> be used to specify all enabled packages. Or ``$(call ptx/collection,
> - $(PTXDIST_WORKSPACE)/configs/<collection-file-name>)`` can be uses to to
> + $(PTXDIST_WORKSPACE)/configs/<collection-file-name>)`` can be used to to
> specify the packages enabled by this collection. In both cases ``=`` must
> - be uses instead of ``:=`` due to the makefile include order.
> + be used instead of ``:=`` due to the makefile include order.
>
> ``<PKG>_CONFIG``
> ``genimage`` packages use this to specify the ``genimage`` configuration
> diff --git a/rules/other/Toplevel.make b/rules/other/Toplevel.make
> index f1a13d72f..ac2289431 100644
> --- a/rules/other/Toplevel.make
> +++ b/rules/other/Toplevel.make
> @@ -203,7 +203,7 @@ endif
> #
> # Pattern target to allow printing variable
> # $(filter ..) is used to match against all existing variables so patterns
> -# containing '%' can be uses to print multiple variables.
> +# containing '%' can be used to print multiple variables.
> # In verbose mode, '<name>=<value>' is printed.
> # Trying to print undefined variables results in an error unless '-k' is
> # used. In this case an empty value is printed.
Reviewed-by: Alexander Dahl <ada@thorsis.com>
Greets
Alex
next prev parent reply other threads:[~2024-04-09 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 7:37 [ptxdist] [PATCH 0/2] Fix a few typos and duplicated words Markus Heidelberg
2024-04-09 7:37 ` [ptxdist] [PATCH 1/2] Fix typos "can/must be uses" -> "used" Markus Heidelberg
2024-04-09 8:45 ` Alexander Dahl [this message]
2024-04-11 15:04 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-04-09 7:37 ` [ptxdist] [PATCH 2/2] Fix duplicated "to to" in texts Markus Heidelberg
2024-04-09 8:42 ` Alexander Dahl
2024-04-11 15:04 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240409-patchwork-balmy-42af6b4a5962@thorsis.com \
--to=ada@thorsis.com \
--cc=m.heidelberg@cab.de \
--cc=ptxdist@pengutronix.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