From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"xypron.glpk@gmx.de" <xypron.glpk@gmx.de>,
"Carsey, Jaben" <jaben.carsey@intel.com>,
"Gao, Zhichao" <zhichao.gao@intel.com>
Cc: "Ni, Ray" <ray.ni@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>,
Stephano Cetola <stephano.cetola@linux.intel.com>
Subject: Re: [edk2-devel] [PATCH v3 1/1] ShellPkg/CommandLib: avoid NULL derefence and memory leak
Date: Tue, 3 Sep 2019 04:59:57 +0000 [thread overview]
Message-ID: <02A34F284D1DA44BB705E61F7180EF0AAEE88D63@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <d0a8c975-7b58-186d-4bf4-bc481f7aa452@gmx.de>
From https://github.com/tianocore/edk2/blob/master/Maintainers.txt:
M: Jaben Carsey <jaben.carsey@intel.com>
M: Ray Ni <ray.ni@intel.com>
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Heinrich Schuchardt
Sent: Monday, September 2, 2019 3:15 AM
To: Carsey, Jaben <jaben.carsey@intel.com>; devel@edk2.groups.io; Gao, Zhichao <zhichao.gao@intel.com>
Cc: Ni, Ray <ray.ni@intel.com>; Leif Lindholm <leif.lindholm@linaro.org>; Gao, Liming <liming.gao@intel.com>; Stephano Cetola <stephano.cetola@linux.intel.com>
Subject: Re: [edk2-devel] [PATCH v3 1/1] ShellPkg/CommandLib: avoid NULL derefence and memory leak
On 5/10/19 4:32 PM, Carsey, Jaben wrote:
> Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
>
> Code change looks good visually.
Somehow this patch
https://edk2.groups.io/g/devel/message/40395
was never merged.
Who is the maintainer for the ShellPkg?
Best regards
Heinrich
next prev parent reply other threads:[~2019-09-03 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 3:24 [PATCH v3 1/1] ShellPkg/CommandLib: avoid NULL derefence and memory leak Heinrich Schuchardt
2019-05-10 14:32 ` [edk2-devel] " Carsey, Jaben
2019-09-02 10:14 ` Heinrich Schuchardt
2019-09-03 4:59 ` Nate DeSimone [this message]
2019-09-03 7:14 ` Liming Gao
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-list 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=02A34F284D1DA44BB705E61F7180EF0AAEE88D63@ORSMSX114.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/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