From: Hector Marco-Gisbert <hecmargi@upv.es>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>,
Jan-Simon <dl9pf@gmx.de>,
linux-fsdevel@vger.kernel.org, kees Cook <keescook@chromium.org>,
Ismael Ripoll <iripoll@disca.upv.es>
Subject: Re: [PATCH] mm/x86: AMD Bulldozer ASLR fix
Date: Fri, 27 Mar 2015 16:06:53 +0100 [thread overview]
Message-ID: <5515720D.6090005@upv.es> (raw)
In-Reply-To: <20150327144438.GA3254@pd.tnic>
>> Signed-off-by: Hector Marco-Gisbert <hecmargi@upv.es>
>> Signed-off-by: Ismael Ripoll <iripoll@disca.upv.es>
>
> How am I to interpret Ismael's SOB here?
>
> Did he write the patch, did he create it, ...?
>
> Because this SOB chain is incorrect in this form. We have only one
> author per commit. If you want to accredit Ismael, you can say:
>
> Originally-by: Ismael
> Based-on-a-patch-by: Ismael
> Suggested-by: ...
>
> and so on.
Mentored-by: Ismael Ripoll <iripoll@disca.upv.es>
Thank you.
next prev parent reply other threads:[~2015-03-27 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 18:00 [PATCH] mm/x86: AMD Bulldozer ASLR fix Hector Marco-Gisbert
2015-03-24 19:15 ` Borislav Petkov
2015-03-25 18:29 ` Hector Marco
2015-03-25 18:36 ` Hector Marco-Gisbert
2015-03-26 19:08 ` Borislav Petkov
2015-03-27 11:38 ` Hector Marco-Gisbert
2015-03-27 12:14 ` Ingo Molnar
2015-03-27 12:35 ` Borislav Petkov
2015-03-27 14:44 ` Borislav Petkov
2015-03-27 15:06 ` Hector Marco-Gisbert [this message]
2015-03-28 13:10 ` Kees Cook
2015-03-29 8:51 ` Ingo Molnar
2015-03-29 9:53 ` Borislav Petkov
2015-03-31 7:59 ` Ingo Molnar
2015-03-31 12:37 ` [tip:x86/mm] x86/mm: Improve AMD Bulldozer ASLR workaround tip-bot for Hector Marco-Gisbert
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=5515720D.6090005@upv.es \
--to=hecmargi@upv.es \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dl9pf@gmx.de \
--cc=hpa@zytor.com \
--cc=iripoll@disca.upv.es \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.