From: Ge Song <songgebird@gmail.com>
To: edk2-devel@lists.01.org
Cc: Ge Song <songgebird@gmail.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v2 0/1] Fix stack switching to permanent memory
Date: Tue, 5 Sep 2017 22:54:18 +0800 [thread overview]
Message-ID: <20170905145419.3095-1-songgebird@gmail.com> (raw)
Here are changes from v1 patch:
* Revise improper descriptions in subject and commit message
* Remove some debug information to compact the message
* Add a description of practical consequences of the bug
Repo: https://github.com/sgbird/edk2.git
Branch: stack_switch
Best Regards,
Ge Song
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Ge Song (1):
OvmfPkg/SecMain: Fix stack switching to permanent memory
OvmfPkg/Sec/SecMain.c | 2 ++
1 file changed, 2 insertions(+)
--
2.11.0
next reply other threads:[~2017-09-05 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 14:54 Ge Song [this message]
2017-09-05 14:54 ` [PATCH v2 1/1] OvmfPkg/SecMain: Fix stack switching to permanent memory Ge Song
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=20170905145419.3095-1-songgebird@gmail.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