From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Piotr Maziarz <piotrx.maziarz@linux.intel.com>,
Lawrence Hileman <larry.hileman@xconn-tech.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Bob Moore <robert.moore@intel.com>
Subject: linux-next: Signed-off-by missing for commits in the pm tree
Date: Tue, 19 Apr 2022 07:01:16 +1000 [thread overview]
Message-ID: <20220419070116.2974bddb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
Hi all,
Commits
6eaf08770ee8 ("ACPICA: executer/exsystem: Warn about sleeps greater than 10 ms")
ace8f1c54a02 ("ACPICA: executer/exsystem: Inform users about ACPI spec violation")
1838ffe7001b ("ACPICA: executer/exsystem: Add units to time variable names")
8bd24835db17 ("ACPICA: iASL: NHLT: Rename linux specific strucures to device_info")
ab1ba87bd71a ("ACPICA: iASL: NHLT: Fix parsing undocumented bytes at the end of Endpoint Descriptor")
90037551c68d ("ACPICA: iASL: NHLT: Treat Terminator as specific_config")
a95d2fb08538 ("ACPICA: Add the subtable CFMWS to the CEDT table")
62b32fd961cf ("ACPICA: Add support for the Windows 11 _OSI string")
are missing a Signed-off-by from their authors.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-18 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 21:01 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-03 21:15 linux-next: Signed-off-by missing for commits in the pm tree Stephen Rothwell
2022-01-03 21:21 ` Jessica Clarke
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=20220419070116.2974bddb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=larry.hileman@xconn-tech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=piotrx.maziarz@linux.intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
/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