From: David Gibson <david@gibson.dropbear.id.au>
To: Bingwu Zhang <xtex@envs.net>
Cc: devicetree-compiler@vger.kernel.org,
Bingwu Zhang <xtexchooser@duck.com>,
devicetree@vger.kernel.org, ~xtex/staging@lists.sr.ht
Subject: Re: [PATCH 2/2] libfdt: Remove extra semi-colons outside functions
Date: Mon, 18 Nov 2024 14:32:07 +1100 [thread overview]
Message-ID: <Zzq1N-LqqKhe-8IN@zatzit> (raw)
In-Reply-To: <20241116101228.164707-6-xtex@envs.net>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
On Sat, Nov 16, 2024 at 06:12:28PM +0800, Bingwu Zhang wrote:
> From: Bingwu Zhang <xtexchooser@duck.com>
>
> When compiling with -Werror -Wpedantic, both GCC and Clang fails, saying
> that these semi-colons are redundant, so remove them.
>
> Signed-off-by: Bingwu Zhang <xtexchooser@duck.com>
Applied, thanks.
> ---
> libfdt/fdt_overlay.c | 2 +-
> libfdt/libfdt.h | 20 ++++++++++----------
> 2 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/libfdt/fdt_overlay.c b/libfdt/fdt_overlay.c
> index f9be13865807..1b098e61c270 100644
> --- a/libfdt/fdt_overlay.c
> +++ b/libfdt/fdt_overlay.c
> @@ -352,7 +352,7 @@ static int overlay_fixup_one_phandle(void *fdt, void *fdto,
> name, name_len, poffset,
> &phandle_prop,
> sizeof(phandle_prop));
> -};
> +}
>
> /**
> * overlay_fixup_phandle - Set an overlay phandle to the base one
> diff --git a/libfdt/libfdt.h b/libfdt/libfdt.h
> index 96782bc57b84..2e182ea3314d 100644
> --- a/libfdt/libfdt.h
> +++ b/libfdt/libfdt.h
> @@ -263,16 +263,16 @@ int fdt_next_subnode(const void *fdt, int offset);
> struct fdt_header *fdth = (struct fdt_header *)fdt; \
> fdth->name = cpu_to_fdt32(val); \
> }
> -fdt_set_hdr_(magic);
> -fdt_set_hdr_(totalsize);
> -fdt_set_hdr_(off_dt_struct);
> -fdt_set_hdr_(off_dt_strings);
> -fdt_set_hdr_(off_mem_rsvmap);
> -fdt_set_hdr_(version);
> -fdt_set_hdr_(last_comp_version);
> -fdt_set_hdr_(boot_cpuid_phys);
> -fdt_set_hdr_(size_dt_strings);
> -fdt_set_hdr_(size_dt_struct);
> +fdt_set_hdr_(magic)
> +fdt_set_hdr_(totalsize)
> +fdt_set_hdr_(off_dt_struct)
> +fdt_set_hdr_(off_dt_strings)
> +fdt_set_hdr_(off_mem_rsvmap)
> +fdt_set_hdr_(version)
> +fdt_set_hdr_(last_comp_version)
> +fdt_set_hdr_(boot_cpuid_phys)
> +fdt_set_hdr_(size_dt_strings)
> +fdt_set_hdr_(size_dt_struct)
> #undef fdt_set_hdr_
>
> /**
--
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 --]
prev parent reply other threads:[~2024-11-18 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 10:12 [PATCH 0/2] libfdt: Fix -Wextra -Wpedantic warnings Bingwu Zhang
2024-11-16 10:12 ` [PATCH 1/2] libfdt: Suppress a unused parameter warning in overlay_fixup_one_phandle Bingwu Zhang
2024-11-18 3:25 ` David Gibson
2024-11-18 10:15 ` xtex
2024-11-18 10:15 ` xtex
2024-11-16 10:12 ` [PATCH 2/2] libfdt: Remove extra semi-colons outside functions Bingwu Zhang
2024-11-18 3:32 ` David Gibson [this message]
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=Zzq1N-LqqKhe-8IN@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=xtex@envs.net \
--cc=xtexchooser@duck.com \
--cc=~xtex/staging@lists.sr.ht \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox