From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/6] efi_loader: Initial HII database protocols
Date: Fri, 2 Nov 2018 09:32:16 +0900 [thread overview]
Message-ID: <20181102003215.GP11663@linaro.org> (raw)
In-Reply-To: <1252e00b-eaec-fecb-9ac7-4a49555b0a37@gmx.de>
On Thu, Nov 01, 2018 at 08:39:04AM +0100, Heinrich Schuchardt wrote:
> On 11/01/2018 05:47 AM, AKASHI Takahiro wrote:
> > From: Leif Lindholm <leif.lindholm@linaro.org>
> >
> > This patch provides enough implementation of the following protocols to
> > run EDKII's Shell.efi and UEFI SCT:
> >
> > * EfiHiiDatabaseProtocol
> > * EfiHiiStringProtocol
> >
> > Not implemented are:
> > * ExportPackageLists()
> > * RegisterPackageNotify()/UnregisterPackageNotify()
> > * SetKeyboardLayout() (i.e. *current* keyboard layout)
> >
>
> <snip />
>
> > + case EFI_HII_PACKAGE_STRINGS:
> > + ret = add_strings_package(hii,
> > + (struct efi_hii_strings_package *)package);
>
> scripts/checkpatch.pl:
>
> CHECK: Alignment should match open parenthesis
> #583: FILE: lib/efi_loader/efi_hii.c:231:
> + ret = add_strings_package(hii,
> + (struct efi_hii_strings_package *)package);
I've noticed this warning as well as another type of warning, such as
CHECK: Lines should not end with a '('
#186: FILE: include/efi_api.h:832:
+ efi_status_t(EFIAPI *new_package_list)(
CHECK: spaces preferred around that '*' (ctx:WxV)
#186: FILE: include/efi_api.h:832:
+ efi_status_t(EFIAPI *new_package_list)(
Those are quite difficult to fix without sacrificing readability
or introducing another warning.
If you have any solution, please let me know.
| case EFI_HII_PACKAGE_STRINGS:
| struct efi_hii_strings_package *strings_package;
|
| strings_package = (struct efi_hii_strings_package *)package);
| ret = add_strings_package(hii, strings_package);
|
This kinda fix is a non-sense, I believe.
-Takahiro Akashi
> Please, adjust the alignment.
>
> Best regards
>
> Heinrich
next prev parent reply other threads:[~2018-11-02 0:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 4:40 [U-Boot] [PATCH 0/6] efi_loader: add HII database protocol AKASHI Takahiro
2018-11-01 4:45 ` [U-Boot] [PATCH 1/6] lib: add u16_strcpy/strdup functions AKASHI Takahiro
2018-11-01 6:10 ` Heinrich Schuchardt
2018-11-02 0:12 ` AKASHI Takahiro
2018-11-01 4:47 ` [U-Boot] [PATCH 2/6] efi_loader: Initial HII database protocols AKASHI Takahiro
2018-11-01 4:47 ` [U-Boot] [PATCH 3/6] efi: hii: add guid package support AKASHI Takahiro
2018-11-01 4:47 ` [U-Boot] [PATCH 4/6] efi: hii: add keyboard layout " AKASHI Takahiro
2018-11-01 4:47 ` [U-Boot] [PATCH 5/6] efi: hii: add HII config routing/access protocols AKASHI Takahiro
2018-11-01 4:47 ` [U-Boot] [PATCH 6/6] efi_selftest: add HII database protocols test AKASHI Takahiro
2018-11-01 7:33 ` Heinrich Schuchardt
2018-11-02 0:55 ` AKASHI Takahiro
2018-11-02 8:12 ` Heinrich Schuchardt
2018-11-01 7:09 ` [U-Boot] [PATCH 2/6] efi_loader: Initial HII database protocols Heinrich Schuchardt
2018-11-02 2:03 ` AKASHI Takahiro
2018-11-01 7:39 ` Heinrich Schuchardt
2018-11-02 0:32 ` AKASHI Takahiro [this message]
2018-11-02 8:15 ` Heinrich Schuchardt
2018-11-01 8:42 ` Heinrich Schuchardt
2018-11-02 0:17 ` AKASHI Takahiro
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=20181102003215.GP11663@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
/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