From: Kees Cook <kees@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Tamir Duberstein <tamird@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>, gldrk <me@rarity.fan>,
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 pm tree
Date: Wed, 30 Apr 2025 11:36:00 -0700 [thread overview]
Message-ID: <202504301135.17AD266A98@keescook> (raw)
In-Reply-To: <4654171.LvFx2qVVIh@rjwysocki.net>
On Wed, Apr 30, 2025 at 08:32:25PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, April 30, 2025 1:30:43 AM CEST Tamir Duberstein wrote:
> > On Tue, Apr 29, 2025 at 3:55 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > Commits
> > >
> > > 9eef70365d71 ("ACPICA: Introduce ACPI_NONSTRING")
> > > ac9334785c75 ("ACPICA: utilities: Fix overflow check in vsnprintf()")
> > > 5de20bc939b0 ("ACPICA: Apply pack(1) to union aml_resource")
> > >
> > > are missing a Signed-off-by from their authors.
> >
> > Hi Stephen, how can I remedy this for 5de20bc939b0 ("ACPICA: Apply
> > pack(1) to union aml_resource")?
>
> The original ACPICA commit does not carry an S-o-b from you, so this one
> does not either.
>
> If you reply with a Signed-off-by to this message:
>
> https://lore.kernel.org/linux-acpi/4664267.LvFx2qVVIh@rjwysocki.net/
>
> I will pick up your tag.
Whoops, mine is missed too from ACPICA upstream. I've replied now to
https://lore.kernel.org/linux-acpi/1841930.VLH7GnMWUR@rjwysocki.net/
--
Kees Cook
next prev parent reply other threads:[~2025-04-30 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 22:55 linux-next: Signed-off-by missing for commit in the pm tree 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 [this message]
2025-04-30 18:53 ` Tamir Duberstein
-- strict thread matches above, loose matches on Subject: below --
2025-05-08 21:44 Stephen Rothwell
2024-09-02 22:21 Stephen Rothwell
2024-09-03 7:11 ` Adrien Destugues
2024-06-30 23:15 Stephen Rothwell
2024-07-01 15:23 ` Mario Limonciello
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=202504301135.17AD266A98@keescook \
--to=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=me@rarity.fan \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
--cc=tamird@gmail.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;
as well as URLs for NNTP newsgroup(s).