From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the arm tree
Date: Mon, 7 Jun 2021 12:49:48 +0100 [thread overview]
Message-ID: <20210607114946.GD22278@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210604081503.2229b376@canb.auug.org.au>
On Fri, Jun 04, 2021 at 08:15:03AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> aafc8eb78635 ("ARM: update __swp_entry_to_pte() to use PTE_TYPE_FAULT")
>
> is missing a Signed-off-by from its author and committer.
For the record... as mentioned on irc, this looks perfectly fine to me:
commit aafc8eb78635a2ecb612653f57f1e86e9030b5d9
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
AuthorDate: Thu May 13 11:53:17 2021 +0100
Commit: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
CommitDate: Thu Jun 3 11:39:02 2021 +0100
...
Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
It seems that the author and committer do indeed have the appropriate
sign-off in place on this commit.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-06-07 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 22:15 linux-next: Signed-off-by missing for commit in the arm tree Stephen Rothwell
2021-06-07 11:49 ` Russell King (Oracle) [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-19 1:18 Stephen Rothwell
2020-01-19 15:08 ` Russell King - ARM Linux admin
2019-09-10 14:14 Stephen Rothwell
2019-09-10 14:21 ` Russell King - ARM Linux admin
2019-09-11 14:21 ` Mike Rapoport
2019-09-11 14:41 ` Stephen Rothwell
2019-09-11 16:04 ` Russell King - ARM Linux admin
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=20210607114946.GD22278@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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 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.