All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH] Remove duplicated words in documentation and comments
Date: Fri, 14 Mar 2025 13:48:48 +1100	[thread overview]
Message-ID: <Z9OZEMY0iD9FNEO2@zatzit> (raw)
In-Reply-To: <20250313190527.1556019-1-thuth@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]

On Thu, Mar 13, 2025 at 08:05:27PM +0100, Thomas Huth wrote:
> Let's avoid repeating single words here!
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>

Applied, thanks.

What brings you to making dtc patches?

> ---
>  CONTRIBUTING.md                      | 2 +-
>  Documentation/dt-object-internal.txt | 2 +-
>  libfdt/libfdt.h                      | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
> index 940dd1a..48c8efd 100644
> --- a/CONTRIBUTING.md
> +++ b/CONTRIBUTING.md
> @@ -2,7 +2,7 @@
>  
>  There are two ways to submit changes for dtc or libfdt:
>  
> -* Post patches directly to the the
> +* Post patches directly to the
>    [devicetree-compiler](mailto:devicetree-compiler@vger.kernel.org)
>    mailing list.
>  * Submit pull requests via
> diff --git a/Documentation/dt-object-internal.txt b/Documentation/dt-object-internal.txt
> index c7357e6..dbbbcea 100644
> --- a/Documentation/dt-object-internal.txt
> +++ b/Documentation/dt-object-internal.txt
> @@ -6,7 +6,7 @@ the hardware capabilities. This is insufficient for platforms
>  that need to dynamically insert Device Tree fragments into the
>  live tree.
>  
> -This document explains the the Device Tree object format and
> +This document explains the Device Tree object format and
>  modifications made to the Device Tree compiler, which make it possible.
>  
>  1. Simplified Problem Definition
> diff --git a/libfdt/libfdt.h b/libfdt/libfdt.h
> index f2675b1..b5e7200 100644
> --- a/libfdt/libfdt.h
> +++ b/libfdt/libfdt.h
> @@ -1569,7 +1569,7 @@ static inline int fdt_property_cell(void *fdt, const char *name, uint32_t val)
>   * @fdt: pointer to the device tree blob
>   * @name: name of property to add
>   * @len: length of property value in bytes
> - * @valp: returns a pointer to where where the value should be placed
> + * @valp: returns a pointer to where the value should be placed
>   *
>   * returns:
>   *	0, on success

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-03-14  3:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 19:05 [PATCH] Remove duplicated words in documentation and comments Thomas Huth
2025-03-14  2:48 ` David Gibson [this message]
2025-03-14  5:27   ` Thomas Huth

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=Z9OZEMY0iD9FNEO2@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=thuth@redhat.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 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.