linux-kernel - Re: linux-next: Signed-off-by missing for commits in the amlogic tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 19 Jul 2018 14:26:47 -0500
From:   Kevin Hilman <khilman@...libre.com>
To:     arm@...nel.org, Olof Johansson <olof@...om.net>
Cc:     Carlo Caione <carlo@...one.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: linux-next: Signed-off-by missing for commits in the amlogic tree

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> Commits
>
>   3f1ad8c53b29 ("ARM64: dts: meson: enable the saradc node in meson-gx-p23x-q20x.dtsi")
>   4dabd157d48e ("ARM64: dts: meson-gx-p23x-q20x: move the wifi node to each board's .dts")
>
> are missing a Signed-off-by from their committer.

Oops.  I missed these.

Olof, these were just merged by you in my PR[1].  How do you want me to
handle this?

I could respin the PR, or just send another with them reverted then
re-applied with signoff?

Or, since these branches don't need to be static (yet), I suppose you
could just edit the commits and add my signoff.  

I'm OK with any of the above, let me know your preferene.

Kevin

[1] https://marc.info/?l=linux-arm-kernel&m=153184268320170