From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH] efi_loader: Remove unnecessary debug
Date: Thu, 21 May 2020 09:13:32 +0900 [thread overview]
Message-ID: <20200521001332.GA21353@laputa> (raw)
In-Reply-To: <aad6cf10-8437-61ef-9057-cd1f222296fd@gmx.de>
On Tue, May 19, 2020 at 12:24:27PM +0200, Heinrich Schuchardt wrote:
> On 19.05.20 12:13, Pragnesh Patel wrote:
> > Remove unnecessary debug() from efi_set_variable_common().
> > native_name is NULL, so there is no meaning to print it.
> >
> > Signed-off-by: Pragnesh Patel <pragnesh.patel@sifive.com>
>
> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Nak
> > lib/efi_loader/efi_variable.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/lib/efi_loader/efi_variable.c b/lib/efi_loader/efi_variable.c
> > index 10892684d1..9698efbc5d 100644
> > --- a/lib/efi_loader/efi_variable.c
> > +++ b/lib/efi_loader/efi_variable.c
> > @@ -883,8 +883,6 @@ static efi_status_t efi_set_variable_common(u16 *variable_name,
> > u32 attr;
> > efi_status_t ret = EFI_SUCCESS;
> >
> > - debug("%s: set '%s'\n", __func__, native_name);
Instead,
debug("%s: set '%ls'\n", __func__, variable_name);
It would be helpful for tracing activities.
This function can be used outside of this file, particularly,
to handle READ_ONLY variables there.
-Takahiro Akashi
> > -
> > if (!variable_name || !*variable_name || !vendor ||
> > ((attributes & EFI_VARIABLE_RUNTIME_ACCESS) &&
> > !(attributes & EFI_VARIABLE_BOOTSERVICE_ACCESS))) {
> >
>
prev parent reply other threads:[~2020-05-21 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 10:13 [PATCH] efi_loader: Remove unnecessary debug Pragnesh Patel
2020-05-19 10:24 ` Heinrich Schuchardt
2020-05-21 0:13 ` AKASHI Takahiro [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=20200521001332.GA21353@laputa \
--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