mirror of https://gitlab.com/qemu-project/dtc.git
Remove duplicated words in documentation and comments
Let's avoid repeating single words here! Signed-off-by: Thomas Huth <thuth@redhat.com> Message-ID: <20250313190527.1556019-1-thuth@redhat.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
This commit is contained in:
parent
dd1b3e532d
commit
da85f91931
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue