From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Rong Tao" <rtoax@foxmail.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"open list:EXTENSIBLE FIRMWARE INTERFACE (EFI)"
<linux-efi@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Cc: rongtao@cestc.cn
Subject: Re: [PATCH] efi: efi.h: Remove extra semicolon
Date: Tue, 19 May 2026 17:25:42 +0200 [thread overview]
Message-ID: <b2eaed8f-efea-40c5-bcf3-6f3cecd38a6d@app.fastmail.com> (raw)
In-Reply-To: <tencent_270AE22BC7E81D6281019A105796C8E5AE06@qq.com>
On Mon, 18 May 2026, at 09:02, Rong Tao wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> Remove extra semicolons from comments.
>
> Signed-off-by: Rong Tao <rongtao@cestc.cn>
> ---
> include/linux/efi.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/efi.h b/include/linux/efi.h
> index 72e76ec54641..ccbc35479684 100644
> --- a/include/linux/efi.h
> +++ b/include/linux/efi.h
> @@ -61,7 +61,7 @@ typedef void *efi_handle_t;
>
> /*
> * The UEFI spec and EDK2 reference implementation both define EFI_GUID as
> - * struct { u32 a; u16; b; u16 c; u8 d[8]; }; and so the implied alignment
> + * struct { u32 a; u16 b; u16 c; u8 d[8]; }; and so the implied alignment
> * is 32 bits not 8 bits like our guid_t. In some cases (i.e., on 32-bit ARM),
> * this means that firmware services invoked by the kernel may assume that
> * efi_guid_t* arguments are 32-bit aligned, and use memory accessors that
> --
> 2.54.0
Thanks, queued up now.
prev parent reply other threads:[~2026-05-19 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 7:02 [PATCH] efi: efi.h: Remove extra semicolon Rong Tao
2026-05-19 15:25 ` Ard Biesheuvel [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=b2eaed8f-efea-40c5-bcf3-6f3cecd38a6d@app.fastmail.com \
--to=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
/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