From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: linux-next: Signed-off-by missing for commit in the pinctrl tree
Date: Wed, 16 May 2018 13:33:20 +0200 [thread overview]
Message-ID: <CACRpkdZTMqf0sFCMPaX2aAcxrJ3LXAi7-Cfx5qevvp7To0V6NA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVPonsrrmEeTmBR+3YW65hSaHbVOz-8_A10cLoAd2SXyw@mail.gmail.com>
On Wed, May 16, 2018 at 1:29 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Wed, May 16, 2018 at 1:24 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Wed, May 16, 2018 at 9:16 AM, Geert Uytterhoeven
>> <geert@linux-m68k.org> wrote:
>>> On Tue, May 15, 2018 at 11:27 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>> Commit
>>>>
>>>> f18fab4bcb4f ("pinctrl: sh-pfc: Add r8a77470 PFC support")
>>>>
>>>> is missing a Signed-off-by from its comitter.
>>>
>>> Sorry, I forgot to add it.
>>>
>>> Linus, as the merge of sh-pfc is your top commit, shall I fix it up
>>> and send a new
>>> pull request?
>>> Please let me know how to proceed. Thanks!
>>
>> If it's just missing your SoB I can add it with your permission
>> I guess? That is less trouble.
>
> You have my permission.
> But I'm afraid that won't help, as then you'll become the committer with your
> SoB missing...
Bah I just sign them all off then. It's still quicker.
Done!
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-05-16 11:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 21:27 linux-next: Signed-off-by missing for commit in the pinctrl tree Stephen Rothwell
2018-05-16 7:16 ` Geert Uytterhoeven
2018-05-16 11:24 ` Linus Walleij
2018-05-16 11:29 ` Geert Uytterhoeven
2018-05-16 11:33 ` Linus Walleij [this message]
2018-05-16 17:40 ` Geert Uytterhoeven
2018-05-23 9:49 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2022-04-21 22:32 Stephen Rothwell
2022-04-22 20:58 ` Linus Walleij
2021-04-07 22:46 Stephen Rothwell
2020-04-16 22:30 Stephen Rothwell
2020-04-17 10:25 ` Linus Walleij
2019-09-11 10:48 Stephen Rothwell
2019-09-12 9:26 ` Linus Walleij
2018-07-09 21:54 Stephen Rothwell
2018-07-09 22:46 ` Linus Walleij
2018-07-10 1:18 ` Yoshihiro Shimoda
2018-07-10 7:07 ` Geert Uytterhoeven
2018-03-07 20:39 Stephen Rothwell
2018-03-07 22:25 ` Linus Walleij
2018-03-08 0:36 ` Stephen Rothwell
2018-03-08 7:05 ` Geert Uytterhoeven
2018-03-08 12:04 ` Linus Walleij
2018-03-03 4:52 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=CACRpkdZTMqf0sFCMPaX2aAcxrJ3LXAi7-Cfx5qevvp7To0V6NA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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.