Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <7h4lgvm3go.fsf@baylibre.com>
References: <20180716080014.75c9016b@canb.auug.org.au> <7h4lgvm3go.fsf@baylibre.com>
From:   Olof Johansson <olof@lixom.net>
Date:   Thu, 19 Jul 2018 14:57:19 -0700
Message-ID: <CAOesGMghENGioK2o_dZKGPJYT01yoP9Fks1k-i1SUXZFENu3Lg@mail.gmail.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the amlogic tree
To:     Kevin Hilman <khilman@baylibre.com>
Cc:     ARM-SoC Maintainers <arm@kernel.org>,
        Carlo Caione <carlo@caione.org>,
        Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Stephen Rothwell <sfr@canb.auug.org.au>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Jul 19, 2018 at 12:26 PM, Kevin Hilman <khilman@baylibre.com> wrote:
> Stephen Rothwell <sfr@canb.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.

Hi,

Fresh pull requests is probably easiest for all. I'll drop the one I brought in.


-Olof