Let's avoid repeating single words here! Signed-off-by: Thomas Huth <thuth@xxxxxxxxxx> --- 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@xxxxxxxxxxxxxxx) 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
