From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Rapoport <mike.rapoport@gmail.com>,
Mike Rapoport <rppt@linux.ibm.com>, Chester Lin <clin@suse.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the arm tree
Date: Tue, 10 Sep 2019 15:21:28 +0100 [thread overview]
Message-ID: <20190910142128.GR13294@shell.armlinux.org.uk> (raw)
In-Reply-To: <20190911001459.6ccc76ee@canb.auug.org.au>
This is correctly signed off, but Mike didn't send the patch correctly.
It missed a From: line for the proper author, so the patch was committed
as if Mike had authored it, which he didn't.
On Wed, Sep 11, 2019 at 12:14:59AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 2505b9ba9c37 ("ARM: 8904/1: skip nomap memblocks while finding the lowmem/highmem boundary")
>
> is missing a Signed-off-by from its author.
>
> --
> Cheers,
> Stephen Rothwell
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-09-10 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 14:14 linux-next: Signed-off-by missing for commit in the arm tree Stephen Rothwell
2019-09-10 14:21 ` Russell King - ARM Linux admin [this message]
2019-09-11 14:21 ` Mike Rapoport
2019-09-11 14:41 ` Stephen Rothwell
2019-09-11 16:04 ` Russell King - ARM Linux admin
2020-01-19 1:18 Stephen Rothwell
2020-01-19 15:08 ` Russell King - ARM Linux admin
2021-06-03 22:15 Stephen Rothwell
2021-06-07 11:49 ` Russell King (Oracle)
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=20190910142128.GR13294@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=clin@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mike.rapoport@gmail.com \
--cc=rppt@linux.ibm.com \
--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).