* [PATCH] Remove duplicated words in documentation and comments
@ 2025-03-13 19:05 Thomas Huth
2025-03-14 2:48 ` David Gibson
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Huth @ 2025-03-13 19:05 UTC (permalink / raw)
To: devicetree-compiler; +Cc: Thomas Huth
Let's avoid repeating single words here!
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
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
--
2.48.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] Remove duplicated words in documentation and comments
2025-03-13 19:05 [PATCH] Remove duplicated words in documentation and comments Thomas Huth
@ 2025-03-14 2:48 ` David Gibson
2025-03-14 5:27 ` Thomas Huth
0 siblings, 1 reply; 3+ messages in thread
From: David Gibson @ 2025-03-14 2:48 UTC (permalink / raw)
To: Thomas Huth; +Cc: devicetree-compiler
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] Remove duplicated words in documentation and comments
2025-03-14 2:48 ` David Gibson
@ 2025-03-14 5:27 ` Thomas Huth
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2025-03-14 5:27 UTC (permalink / raw)
To: David Gibson; +Cc: devicetree-compiler
On 14/03/2025 03.48, David Gibson wrote:
> 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?
I'm currently trying to clean the __ASSEMBLY__ vs. __ASSEMBLER__ stuff in
the kernel, where I saw that they have a copy of fdt.h in their tree, so the
origin needs to be fixed, too. While checking dtc, I noticed that I had this
long-forgotten patch here sitting in my local copy of the repo since years,
so I thought it would finally be a good point in time to finally send it out :-)
Thomas
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-03-14 5:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-13 19:05 [PATCH] Remove duplicated words in documentation and comments Thomas Huth
2025-03-14 2:48 ` David Gibson
2025-03-14 5:27 ` Thomas Huth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).