From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Signed-off-by missing in the s390 tree
Date: Fri, 16 Oct 2015 09:43:11 +0200 [thread overview]
Message-ID: <20151016094311.33ebf5fb@mschwide> (raw)
In-Reply-To: <20151016091733.30454691@canb.auug.org.au>
On Fri, 16 Oct 2015 09:17:33 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Martin,
>
> I noticed that the top commit
>
> 748a000bdc07 ("s390/fpu: split fpu-internal.h into fpu internals, api, and type headers")
>
> in the s390 tree has no Signed-off-by tag from you as committer ...
Oopsy.. fixed. Thanks for the hint.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2015-10-16 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 22:17 linux-next: Signed-off-by missing in the s390 tree Stephen Rothwell
2015-10-16 7:43 ` Martin Schwidefsky [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=20151016094311.33ebf5fb@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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