[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <D705597A-C89B-4C39-93EF-416193BC3A40@jrtc27.com>
Date: Mon, 3 Jan 2022 21:21:50 +0000
From: Jessica Clarke <jrtc27@...c27.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Bob Moore <robert.moore@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the pm tree
On 3 Jan 2022, at 21:15, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> Commits
>
> a3e525feaeec ("ACPICA: Avoid subobject buffer overflow when validating RSDP signature")
> 339651be3704 ("ACPICA: Macros: Remove ACPI_PHYSADDR_TO_PTR")
> 5d6e59665d8b ("ACPICA: Use original pointer for virtual origin tables")
> ca25f92b72d2 ("ACPICA: Use original data_table_region pointer for accesses")
>
> are missing a Signed-off-by from their author.
They’re commits I contributed from CheriBSD (our research fork of
FreeBSD targeting CHERI/Arm’s Morello prototype as the reference POSIX
OS) to upstream ACPICA. Upstream ACPICA did not ask for S-o-b, and I
don’t see why you should need them to import them into Linux; I highly
doubt every vendored bit of code you’ve vendored downstream has an
associated S-o-b. The patch series (which I was Cc’ed on, and would
rather not have been; Cc’ing any upstream ACPICA contributor with Linux
kernel patches is, to most, spam and obnoxious) is just merging the
newer upstream ACPICA version by extracting the individual upstream
ACPICA commits and mangling them for applying to the kernel.
Jess
Powered by blists - more mailing lists