From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/4] disk: efi: Fix memory leak on 'gpt guid'
Date: Tue, 7 May 2019 10:11:18 +0200 [thread overview]
Message-ID: <20190507101118.06a7f378@jawa> (raw)
In-Reply-To: <20190507071010.GA25260@vmlxhi-102.adit-jv.com>
On Tue, 7 May 2019 09:10:28 +0200
Eugeniu Rosca <erosca@de.adit-jv.com> wrote:
> Hi Lukasz,
>
> On Tue, May 07, 2019 at 09:03:15AM +0200, Lukasz Majewski wrote:
> [..]
> > Reviewed-by: Lukasz Majewski <lukma@denx.de>
> >
> >
> > Best regards,
> >
> > Lukasz Majewski
> >
> > --
> >
> > DENX Software Engineering GmbH, Managing Director: Wolfgang
> > Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
> > Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email:
> > lukma at denx.de
>
> Thanks for the recent reviews.
> FYI, the patches from this series have already been accepted by Tom:
>
> 4ccf678f3773 ("lib: uuid: Fix unseeded PRNG on RANDOM_UUID=y")
> d02660960d78 ("cmd: gpt: fix and tidy up help message")
> 716f919d2da7 ("disk: efi: Fix memory leak on 'gpt verify'")
> 1cfe9694752e ("disk: efi: Fix memory leak on 'gpt guid'")
>
> Thinking of some process optimization, wouldn't it be useful to see a
> message from the delegated maintainer that the patches have been
> applied to his U-Boot fork?
It would be helpful, but the person to be blamed is me :-) I shall
review the patches sooner.
Anyway, thanks for your work as they fix real issues.
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190507/b2081fd1/attachment.sig>
next prev parent reply other threads:[~2019-05-07 8:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 12:27 [U-Boot] [PATCH v2 0/4] Misc EFI/GPT/UUID fixes Eugeniu Rosca
2019-05-02 12:27 ` [U-Boot] [PATCH v2 1/4] disk: efi: Fix memory leak on 'gpt guid' Eugeniu Rosca
2019-05-07 7:03 ` Lukasz Majewski
2019-05-07 7:10 ` Eugeniu Rosca
2019-05-07 8:11 ` Lukasz Majewski [this message]
2019-05-07 12:08 ` Eugeniu Rosca
2019-05-02 12:27 ` [U-Boot] [PATCH v2 2/4] disk: efi: Fix memory leak on 'gpt verify' Eugeniu Rosca
2019-05-07 7:02 ` Lukasz Majewski
2019-05-02 12:27 ` [U-Boot] [PATCH v2 3/4] cmd: gpt: fix and tidy up help message Eugeniu Rosca
2019-05-07 7:01 ` Lukasz Majewski
2019-05-02 12:27 ` [U-Boot] [PATCH v2 4/4] lib: uuid: Fix unseeded PRNG on RANDOM_UUID=y Eugeniu Rosca
2019-05-02 16:19 ` Heinrich Schuchardt
2019-05-07 7:04 ` Lukasz Majewski
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=20190507101118.06a7f378@jawa \
--to=lukma@denx.de \
--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