[PATCH 5/9] image: Fix typos in image.h

Simon Glass sjg at chromium.org
Sun Oct 26 15:27:03 CET 2025


Hi Wolfgang,

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner at br-automation.com> wrote:
>
> Fix some typos in include/image.h.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner at br-automation.com>
> ---
>
>  include/image.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>

Reviewed-by: Simon Glass <sjg at chromium.org>

> diff --git a/include/image.h b/include/image.h
> index fc2f2487095..9a1c828416d 100644
> --- a/include/image.h
> +++ b/include/image.h
> @@ -654,10 +654,10 @@ int boot_get_fpga(struct bootm_headers *images);
>   * boot_get_ramdisk() is responsible for finding a valid ramdisk image.
>   * Currently supported are the following ramdisk sources:
>   *      - multicomponent kernel/ramdisk image,
> - *      - commandline provided address of decicated ramdisk image.
> + *      - commandline provided address of dedicated ramdisk image.

It would be better with a hyphen: commandline-provided

>   *
>   * returns:
> - *     0, if ramdisk image was found and valid, or skiped
> + *     0, if ramdisk image was found and valid, or skipped
>   *     rd_start and rd_end are set to ramdisk start/end addresses if
>   *     ramdisk image is found and valid
>   *
> @@ -739,7 +739,7 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr,
>   * @param bootstage_id ID of starting bootstage to use for progress updates.
>   *                     This will be added to the BOOTSTAGE_SUB values when
>   *                     calling bootstage_mark()
> - * @param load_op      Decribes what to do with the load address
> + * @param load_op      Describes what to do with the load address
>   * @param datap                Returns address of loaded image
>   * @param lenp         Returns length of loaded image
>   * Return: node offset of image, or -ve error code on error:
> @@ -812,7 +812,7 @@ int fit_get_node_from_config(struct bootm_headers *images,
>   * boot_get_fdt() is responsible for finding a valid flat device tree image.
>   * Currently supported are the following FDT sources:
>   *      - multicomponent kernel/ramdisk/FDT image,
> - *      - commandline provided address of decicated FDT image.
> + *      - commandline provided address of dedicated FDT image.
>   *
>   * Return:
>   *     0, if fdt image was found and valid, or skipped
> --
> 2.51.1
>

Regards,
Simon


More information about the U-Boot mailing list