From: Kevin Hilman <khilman@baylibre.com>
To: Olof Johansson <olof@lixom.net>
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>
Subject: Re: linux-next: Signed-off-by missing for commits in the amlogic tree
Date: Fri, 20 Jul 2018 10:22:49 -0500 [thread overview]
Message-ID: <7hh8ku53ue.fsf@baylibre.com> (raw)
In-Reply-To: <CAOesGMghENGioK2o_dZKGPJYT01yoP9Fks1k-i1SUXZFENu3Lg@mail.gmail.com> (Olof Johansson's message of "Thu, 19 Jul 2018 14:57:19 -0700")
Olof Johansson <olof@lixom.net> writes:
> 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.
>
Ack, I'll resend. Thanks.
Kevin
next prev parent reply other threads:[~2018-07-20 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 22:00 linux-next: Signed-off-by missing for commits in the amlogic tree Stephen Rothwell
2018-07-19 19:26 ` Kevin Hilman
2018-07-19 21:57 ` Olof Johansson
2018-07-20 15:22 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-04 6:35 Stephen Rothwell
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=7hh8ku53ue.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arm@kernel.org \
--cc=carlo@caione.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.