From: Stefan Agner <stefan@agner.ch>
To: Russell King <rmk@armlinux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the arm-current tree
Date: Thu, 12 Jul 2018 08:32:47 +0200 [thread overview]
Message-ID: <10a54594d17b6d2fa0e85ced00b4a7d5@agner.ch> (raw)
In-Reply-To: <20180711215644.GA18831@flint.armlinux.org.uk>
On 11.07.2018 23:56, Russell King wrote:
> On Thu, Jul 12, 2018 at 07:38:03AM +1000, Stephen Rothwell wrote:
>> Hi Russell,
>>
>> Commit
>>
>> 6ef09e48c2bc ("ARM: 8780/1: ftrace: Only set kernel memory back to read-only after boot")
>>
>> is missing a Signed-off-by from its author.
>
> Thanks for spotting, but it's worse than that. It does have a sign-off
> from its author, but the authorship wasn't preserved by Stefan Agner
> (no From: line in the email body, as there was in Steven's original
> post to the mailing list.) I'll fix that in the next few days.
Hm, not sure how that exactly happened. I uploaded a patch file
generated by git format-patch using the web interface, there was still a
header:
From a55f4af25b9299f35481bc89982590941aaae612 Mon Sep 17 00:00:00 2001
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Date: Thu, 21 Jun 2018 12:47:10 -0400
Subject: [PATCH] ARM: ftrace: Only set kernel memory back to read-only
after
boot
I probably should have added the line to the message field?
Sorry about that!
--
Stefan
prev parent reply other threads:[~2018-07-12 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 21:38 linux-next: Signed-off-by missing for commit in the arm-current tree Stephen Rothwell
2018-07-11 21:56 ` Russell King
2018-07-12 6:32 ` Stefan Agner [this message]
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=10a54594d17b6d2fa0e85ced00b4a7d5@agner.ch \
--to=stefan@agner.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).