From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
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>
Subject: Re: linux-next: Signed-off-by missing for commit in the pm tree
Date: Tue, 15 May 2018 10:58:47 +0200 [thread overview]
Message-ID: <3798543.7VT4y5RNEA@aspire.rjw.lan> (raw)
In-Reply-To: <20180515082109.3b57619a@canb.auug.org.au>
On Tuesday, May 15, 2018 12:21:09 AM CEST Stephen Rothwell wrote:
>
> --Sig_/LKqNOwcm4.nPHJQHAB_CO6g
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
>
> Hi Rafael,
Hi Stephen,
> Commit
>
> e689ba60f1f0 ("Merge branch 'opp/genpd-pstate-updates' of git://git.kerne=
> l.org/pub/scm/linux/kernel/git/vireshk/pm")
>
> is missing a Signed-off-by from its author and committer.
>
> This is probably because (despite its description) this is not a merge
> commit - it seems to have been flattened in the rebase :-(
Thanks for letting me know!
This commit shouldn't have reached you at all, sorry about that.
Should be fixed now.
Thanks,
Rafael
next prev parent reply other threads:[~2018-05-15 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 22:21 linux-next: Signed-off-by missing for commit in the pm tree Stephen Rothwell
2018-05-15 8:58 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 21:23 Stephen Rothwell
2023-07-11 22:35 Stephen Rothwell
2024-01-04 21:19 Stephen Rothwell
2024-01-05 23:02 ` David McFarland
2024-04-15 22:54 Stephen Rothwell
2024-04-16 17:02 ` Dumbre, Saket
2024-06-30 23:15 Stephen Rothwell
2024-07-01 15:23 ` Mario Limonciello
2024-09-02 22:21 Stephen Rothwell
2024-09-03 7:11 ` Adrien Destugues
2025-04-29 22:55 Stephen Rothwell
2025-04-29 23:30 ` Tamir Duberstein
2025-04-29 23:44 ` Stephen Rothwell
2025-04-30 18:32 ` Rafael J. Wysocki
2025-04-30 18:36 ` Kees Cook
2025-04-30 18:53 ` Tamir Duberstein
2025-05-08 21:44 Stephen Rothwell
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=3798543.7VT4y5RNEA@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).