From: Jordan Justen <jordan.l.justen@intel.com>
To: Ge Song <songgebird@gmail.com>, Laszlo Ersek <lersek@redhat.com>,
edk2-devel@lists.01.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v1 1/1] OvmfPkg/SecMain: Fix stack switching to permanent memory fail
Date: Mon, 04 Sep 2017 09:34:31 -0400 [thread overview]
Message-ID: <150453207055.10722.7097788282280420028@jljusten-skl> (raw)
In-Reply-To: <f724d22c-5ffd-b6ab-23b7-8aa5df8f550d@redhat.com>
On 2017-09-03 16:55:36, Laszlo Ersek wrote:
> On 09/03/17 04:12, Ge Song wrote:
> > In earlier PEI stage, temporary memory(Cache As Ram) is employed as stack
> > and heap. We move them to the new room and do some relocation fixup when
> > permanent memory becomes available. TemporaryRamMigration()
> > is responsible for switching the stack.
>
> [...]
>
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Ge Song <ge.song@hxt-semitech.com>
> > ---
> > OvmfPkg/Sec/SecMain.c | 2 ++
> > 1 file changed, 2 insertions(+)
>
> (No more separate emails, I promise.)
>
> Before you send v2, can you please amend the patch like this:
>
> git commit --amend --author='Ge Song <ge.song@hxt-semitech.com>'
>
> It's OK if you mail it out from another email address, but IMO the git
> authorship should match the first Signed-off-by.
I disagree with this. Unless the individual is well known to the EDK
II community as the owner of both email addresses, I think the author
needs to send it from their author email.
I suppose they can send it from another email, and then reply from
their other email saying they contributed it under the Tianocore
Contribution Agreement, but that sounds like a stretch...
-Jordan
> The commit message body currently does not start with "From: Ge Song
> <ge.song@hxt-semitech.com>", which means that the git authorship and the
> first S-o-b disagree at the moment.
>
> ... If I'm wrong about this, I can be convinced, of course.
>
> Thanks
> Laszlo
next prev parent reply other threads:[~2017-09-04 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 2:12 [PATCH v1 0/1] Fix stack switching to permanent memory fail Ge Song
2017-09-03 2:12 ` [PATCH v1 1/1] OvmfPkg/SecMain: " Ge Song
2017-09-03 4:37 ` Jordan Justen
2017-09-03 20:50 ` Laszlo Ersek
2017-09-03 20:49 ` Laszlo Ersek
2017-09-04 8:54 ` Ge Song
2017-09-04 22:26 ` Laszlo Ersek
2017-09-03 20:52 ` Laszlo Ersek
2017-09-03 20:55 ` Laszlo Ersek
2017-09-04 13:34 ` Jordan Justen [this message]
2017-09-04 15:11 ` Ge Song
2017-09-04 21:25 ` Laszlo Ersek
2017-09-05 17:45 ` Jordan Justen
2017-09-05 18:03 ` Leif Lindholm
2017-09-07 1:42 ` Songge
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=150453207055.10722.7097788282280420028@jljusten-skl \
--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