All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the pinctrl tree
Date: Thu, 8 Mar 2018 11:36:47 +1100	[thread overview]
Message-ID: <20180308113647.75279391@canb.auug.org.au> (raw)
In-Reply-To: <CACRpkdaWd_7QWd7t5i6DvU3_Gu1giR9v2uoqQiLNXVWTPEty8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

Hi Linus,

On Wed, 7 Mar 2018 23:25:48 +0100 Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Wed, Mar 7, 2018 at 9:39 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > Commit
> >
> >   fc08fa6009a0 ("pinctrl: sh-pfc: r8a7795: remove duplicate of CLKOUT pin in pinmux_pins[]")
> >
> > is missing a Signed-off-by from its committer.  
> 
> Looping in Geert,
> 
> I guess this came in through the Renesas PFC pull request.
> 
> Geert do you prefer that I back it all out so you can send me
> a new pull request? Or some other solution?

But you are listed as the committer ...
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-03-08  0:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 20:39 linux-next: Signed-off-by missing for commit in the pinctrl tree Stephen Rothwell
2018-03-07 22:25 ` Linus Walleij
2018-03-08  0:36   ` Stephen Rothwell [this message]
2018-03-08  7:05     ` Geert Uytterhoeven
2018-03-08 12:04     ` 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-05-15 21:27 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
2018-05-16 17:40         ` Geert Uytterhoeven
2018-05-23  9:49           ` 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=20180308113647.75279391@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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.