public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Rafael J. Wysocki" <rjw@rjwysocki•net>
Cc: Mario Limonciello <mario.limonciello@amd•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the pm tree
Date: Mon, 1 Jul 2024 09:15:49 +1000	[thread overview]
Message-ID: <20240701091549.08218e8e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 268 bytes --]

Hi all,

Commits

  c00d476cbcef ("cpufreq: amd-pstate: change cpu freq transition delay for some models")
  c7107750b2ff ("x86/cpufeatures: Add AMD FAST CPPC feature flag")

are missing a Signed-off-by from their committers.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-06-30 23:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30 23:15 Stephen Rothwell [this message]
2024-07-01 15:23 ` linux-next: Signed-off-by missing for commit in the pm tree Mario Limonciello
  -- strict thread matches above, loose matches on Subject: below --
2025-05-08 21:44 Stephen Rothwell
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
2024-09-02 22:21 Stephen Rothwell
2024-09-03  7:11 ` Adrien Destugues
2024-04-15 22:54 Stephen Rothwell
2024-04-16 17:02 ` Dumbre, Saket
2024-01-04 21:19 Stephen Rothwell
2024-01-05 23:02 ` David McFarland
2023-07-11 22:35 Stephen Rothwell
2023-04-10 21:23 Stephen Rothwell
2018-05-14 22:21 Stephen Rothwell
2018-05-15  8:58 ` Rafael J. Wysocki

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=20240701091549.08218e8e@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mario.limonciello@amd$(echo .)com \
    --cc=rjw@rjwysocki$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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