From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Gross <markgross@kernel.org>
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 drivers-x86 tree
Date: Fri, 3 Feb 2023 10:06:28 +0100 [thread overview]
Message-ID: <595e91e0-ae13-471d-2685-5d8f3a49b31c@redhat.com> (raw)
In-Reply-To: <20230203083313.53745bdd@canb.auug.org.au>
Hi,
On 2/2/23 22:33, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 95a579b5c89f ("tools/power/x86/intel-speed-select: v1.14 release")
> 19aceabd7a26 ("tools/power/x86/intel-speed-select: Adjust uncore max/min frequency")
> 75ade1b46b8b ("tools/power/x86/intel-speed-select: Add Emerald Rapid quirk")
> a06644c7dc9b ("tools/power intel-speed-select: Fix display of uncore min frequency")
> 113943d71f54 ("tools/power/x86/intel-speed-select: turbo-freq auto mode with SMT off")
> 9bd3f4d5ca2e ("tools/power/x86/intel-speed-select: cpufreq reads on offline CPUs")
> 61246ca53e17 ("tools/power/x86/intel-speed-select: Use null-terminated string")
> e5bf2623cf49 ("tools/power/x86/intel-speed-select: Remove duplicate dup()")
> 1bf2637725f8 ("tools/power/x86/intel-speed-select: Handle open() failure case")
> 1fd93ae6e2b0 ("tools/power/x86/intel-speed-select: Remove unused non_block flag")
> 74ea37879c89 ("tools/power/x86/intel-speed-select: Remove wrong check in set_isst_id()")
>
> are missing a Signed-off-by from their committer.
My bad, these came from a pull-request but then I had to rebase them
making me the commiter. I've added my S-o-b to these now and I'll push
out a fixed for-next soon.
Thank you for catching this.
Regards,
Hans
next prev parent reply other threads:[~2023-02-03 9:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 21:33 linux-next: Signed-off-by missing for commit in the drivers-x86 tree Stephen Rothwell
2023-02-03 9:06 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-07 23:15 Stephen Rothwell
2023-06-08 9:02 ` Hans de Goede
2021-04-14 13:51 Stephen Rothwell
2021-04-14 13:55 ` Hans de Goede
2021-04-08 12:13 Stephen Rothwell
2021-04-08 14:18 ` Hans de Goede
2019-05-06 13:22 Stephen Rothwell
2019-05-06 14:50 ` Andy Shevchenko
2019-02-23 14:19 Stephen Rothwell
2019-02-23 17:10 ` Darren Hart
2019-02-23 17:52 ` Darren Hart
2019-02-23 22:56 ` Stephen Rothwell
2018-08-18 14:35 Stephen Rothwell
2018-08-19 8:21 ` Hans de Goede
2018-08-19 8:48 ` Stephen Rothwell
2018-06-01 11:36 Stephen Rothwell
2018-06-01 11:40 ` Andy Shevchenko
2018-06-01 12:08 ` Stephen Rothwell
2018-06-01 14:33 ` dvhart
2018-06-01 14:55 ` Andy Shevchenko
2018-06-01 14:38 ` dvhart
2018-06-01 15:26 ` Stephen Rothwell
2018-06-01 16:43 ` Darren Hart
2018-06-01 14:45 ` Andy Shevchenko
2017-08-02 20:37 Stephen Rothwell
2017-08-02 23:57 ` Darren Hart
2017-08-03 0:28 ` Stephen Rothwell
2017-08-03 1:06 ` Linus Torvalds
2017-08-03 15:50 ` Darren Hart
2017-08-05 21:58 ` Darren Hart
2017-08-16 23:21 ` Darren Hart
2017-08-24 20:56 ` Darren Hart
2017-08-04 17:44 ` Junio C Hamano
2017-08-04 17:47 ` Darren Hart
2017-08-03 8:17 ` Andy Shevchenko
2017-08-03 9:27 ` 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=595e91e0-ae13-471d-2685-5d8f3a49b31c@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=markgross@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).