From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] efi: Document #define FOO_PROTOCOL_GUID layout
Date: Thu, 18 Feb 2016 15:10:42 +0000 [thread overview]
Message-ID: <20160218151042.GL2651@codeblueprint.co.uk> (raw)
In-Reply-To: <1455718191-31244-1-git-send-email-pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
(Adding Joe)
On Wed, 17 Feb, at 09:09:51AM, Peter Jones wrote:
> Add a comment documenting why EFI GUIDs are laid out like they are.
> Ideally I'd like to change all the ", " to "," too, but right now the
> format is such that checkpatch won't complain with new ones, and staring
> at checkpatch didn't get me anywhere towards making that work.
>
> Signed-off-by: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> include/linux/efi.h | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/efi.h b/include/linux/efi.h
> index 99b88c5..3c27c88 100644
> --- a/include/linux/efi.h
> +++ b/include/linux/efi.h
> @@ -533,7 +533,22 @@ typedef efi_status_t efi_query_variable_store_t(u32 attributes,
> void efi_native_runtime_setup(void);
>
> /*
> - * EFI Configuration Table and GUID definitions
> + * EFI Configuration Table and GUID definitions
> + *
> + * These should be formatted roughly like the ones in the UEFI SPEC has
> + * them. It makes them easier to grep for, and they look the same when
> + * you're staring at them. Here's the guide:
> + *
> + * GUID: 12345678-1234-1234-1234-123456789012
> + * Spec:
> + * #define EFI_SOME_PROTOCOL_GUID \
> + * {0x12345678,0x1234,0x1234,\
> + * {0x12,0x34,0x12,0x34,0x56,0x78,0x90,0x12}}
> + * Here:
> + * #define SOME_PROTOCOL_GUID \
> + * EFI_GUID(0x12345678, 0x1234, 0x1234, \
> + * 0x12, 0x34, 0x12, 0x34, 0x56, 0x78, 0x90, 0x12)
> + * ^ tab ^tab ^ space
> */
> #define NULL_GUID \
> EFI_GUID(0x00000000, 0x0000, 0x0000, \
We do need some kind of comment to explain that the formatting is
important in this file, but I'm wondering whether Joe has any
suggestions for how to make checkpatch.pl ignore the "," change.
Joe?
prev parent reply other threads:[~2016-02-18 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 14:09 [PATCH] efi: Document #define FOO_PROTOCOL_GUID layout Peter Jones
[not found] ` <1455718191-31244-1-git-send-email-pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-18 15:10 ` Matt Fleming [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=20160218151042.GL2651@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).