From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: Re: [ptxdist] [APPLIED] Fix typos, grammar and missing/superfluous words
Date: Sun, 29 Mar 2026 07:47:06 +0200 [thread overview]
Message-ID: <20260329054706.2505677-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260323101842.14692-1-m.heidelberg@cab.de>
Thanks, applied as c03611b23b00400638af09220f192a2dc75ff62e.
Michael
[sent from post-receive hook]
On Sun, 29 Mar 2026 07:47:06 +0200, Markus Heidelberg <m.heidelberg@cab.de> wrote:
> In documentation, help texts and an error message.
>
> Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> Message-Id: <20260323101842.14692-1-m.heidelberg@cab.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/daily_work.inc b/doc/daily_work.inc
> index 7071a0f1577b..f3bb41915d82 100644
> --- a/doc/daily_work.inc
> +++ b/doc/daily_work.inc
> @@ -26,7 +26,7 @@ tree.
> Configuring the PTXdist Project
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> -.. note:: assumption is here, the directory ``/myprj`` contains a valid PTXdist project.
> +.. note:: assumption is here, the directory ``~/myprj`` contains a valid PTXdist project.
>
> To make PTXdist use of this kernel source tree, instead of an archive we
> can simply create a link now:
> @@ -454,7 +454,7 @@ command line parameters.
> is two times the available CPU cores.
>
> ``-je<number>``
> - this defines the number of packages to be build in parallel. The
> + this defines the number of packages to be built in parallel. The
> default is one package at a time.
>
> ``-j<number>``
> @@ -469,7 +469,7 @@ command line parameters.
>
> A much softer setup is to just use the ``-j<number>`` parameter. This will run
> up to ``<number>`` tasks at the same time which will be spread over everything
> -to do. This will create a system load which is much user friendly. Even the
> +to do. This will create a system load which is much more user friendly. Even the
> filesystem load is smoother with this parameter.
>
> Building in Background
> diff --git a/doc/dev_add_bin_only_files.rst b/doc/dev_add_bin_only_files.rst
> index 9031e437cd4f..265b8c2f41d6 100644
> --- a/doc/dev_add_bin_only_files.rst
> +++ b/doc/dev_add_bin_only_files.rst
> @@ -14,7 +14,7 @@ source code format.
> Add Binary Files File by File
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> -Doing to on a file by file base can happen by just using the ``install_copy``
> +Doing so on a file by file base can happen by just using the ``install_copy``
> macro in the *targetinstall* stage in our own customized rules file.
>
> .. code-block:: none
> diff --git a/doc/ref_make_macros.rst b/doc/ref_make_macros.rst
> index a81d54961298..07d6cb53a4e0 100644
> --- a/doc/ref_make_macros.rst
> +++ b/doc/ref_make_macros.rst
> @@ -254,7 +254,7 @@ The ``<source>`` parameter can be:
> *foo* example package can be a ``$(FOO_DIR)/foo``.
> * a minus sign (``-``). PTXdist uses the <destination>
> parameter in this case to locate the file to copy from.
> - The <destination> is uses a path relative to the :ref:`package install
> + The <destination> is used as path relative to the :ref:`package install
> directory<pkg_pkgdir>`. This only works if the package uses the default
> or a similar *install* stage. For our *foo* example used source file is
> ``<platform-dir>/packages/foo-1.1.0/<destination>``.
> diff --git a/platforms/kernel.in b/platforms/kernel.in
> index 5d4e5e2fe0c8..2c6d906e8bae 100644
> --- a/platforms/kernel.in
> +++ b/platforms/kernel.in
> @@ -100,7 +100,7 @@ choice
> prompt "uImage "
> help
> This is the target for most non ia32 platforms like PowerPC
> - and ARM architectures. Its a compressed image with additional
> + and ARM architectures. It's a compressed image with additional
> embedded information.
>
> config KERNEL_IMAGE_VM
> @@ -128,7 +128,7 @@ choice
> bool
> prompt "Image"
> help
> - This is the target to get the kernel image as an raw uncompressed
> + This is the target to get the kernel image as a raw uncompressed
> binary file.
>
> config KERNEL_IMAGE_SIMPLE
> @@ -294,7 +294,7 @@ config KERNEL_OPENSSL
> bool
> help
> Select this if you're going to build your kernel with support for
> - module signing, IMA etc. where openssl is need as hosttool.
> + module signing, IMA etc. where openssl is needed as hosttool.
>
> Select this if you're unsure, as it won't hurt. It just
> increases the build time.
> diff --git a/platforms/toolchain.in b/platforms/toolchain.in
> index 49c9fddeff56..5bdf1c96ba03 100644
> --- a/platforms/toolchain.in
> +++ b/platforms/toolchain.in
> @@ -7,8 +7,8 @@ config CROSSCHAIN_VENDOR
> prompt "check for specific toolchain vendor"
> default "OSELAS.Toolchain-2020.08"
> help
> - Add here an unique vendor string to ensure this project will
> - be build with the correct toolchain.
> + Add here a unique vendor string to ensure this project will
> + be built with the correct toolchain.
> Leave this entry empty to omit this check.
> To use this feature add a file called 'ptxconfig' to the bin/ folder of
> your toolchain. This file should contain at least one variable definition:
> diff --git a/rules/iptables.in b/rules/iptables.in
> index d98f1ac4e0a1..c52f7009d796 100644
> --- a/rules/iptables.in
> +++ b/rules/iptables.in
> @@ -72,7 +72,7 @@ config IPTABLES_LIBNFNETLINK
> bool
> prompt "configure libnfnetlink"
> help
> - Select if iptables should be build against libnfnetlink
> + Select if iptables should be built against libnfnetlink
>
> config IPTABLES_NFTABLES_COMPAT
> bool
> diff --git a/rules/reproducible.in b/rules/reproducible.in
> index 3f3e6b2695ee..b725e204cf58 100644
> --- a/rules/reproducible.in
> +++ b/rules/reproducible.in
> @@ -19,14 +19,14 @@ config REPRODUCIBLE_TIMESTAMP_PTXDIST
> bool
> prompt "ptxdist version"
> help
> - Use the year and month of the PTXdist version to generated the
> + Use the year and month of the PTXdist version to generate the
> timestamp.
>
> config REPRODUCIBLE_TIMESTAMP_TOOLCHAIN
> bool
> prompt "toolchain version"
> help
> - Use the year and month of the toolchain version to generated the
> + Use the year and month of the toolchain version to generate the
> timestamp. This only works for OSELAS.Toolchain.
> This is useful to keep the timestamp stable across PTXdist
> version updates. When a toolchain update happens, then the
> @@ -54,7 +54,7 @@ config REPRODUCIBLE_TIMESTAMP_STRING
> Supply a custom fake timestamp to be injected to the build.
> The timestamp is passed to 'date --date', e.g. "2018-11-01 UTC".
>
> - Note: the timestamp should contain include the timezone.
> + Note: the timestamp should include the timezone.
> Otherwise timezone changes may produce different results.
>
> endif
> diff --git a/scripts/report/generator.py b/scripts/report/generator.py
> index da0552c04e73..e1a4876224b2 100644
> --- a/scripts/report/generator.py
> +++ b/scripts/report/generator.py
> @@ -136,7 +136,7 @@ node [ shape=point fixedsize=true width=0.1 ];
> tmp = version.split(':')
> if len(tmp) > 2:
> raise ReportException(
> - f'cve-version "{version}" contains more than on ":"')
> + f'cve-version "{version}" contains more than one ":"')
> return tmp[0], tmp[1] if len(tmp) > 1 else '*'
>
> def create_cpe_ids(self, pkg):
prev parent reply other threads:[~2026-03-29 5:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 13:29 [ptxdist] [PATCH 1/2] " Markus Heidelberg via ptxdist
2026-03-16 13:29 ` [ptxdist] [PATCH 2/2] Replace non-ASCII em dash (U+2014) by a usual keyboard dash (hyphen-minus) Markus Heidelberg via ptxdist
2026-03-29 5:47 ` [ptxdist] [APPLIED] " Michael Olbrich
2026-03-23 10:18 ` [ptxdist] [PATCH v2 1/2] Fix typos, grammar and missing/superfluous words Markus Heidelberg via ptxdist
2026-03-29 5:47 ` Michael Olbrich [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=20260329054706.2505677-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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