Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: 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: Wed, 7 Mar 2018 23:25:48 +0100
Message-ID: <CACRpkdaWd_7QWd7t5i6DvU3_Gu1giR9v2uoqQiLNXVWTPEty8w@mail.gmail.com> (raw)
In-Reply-To: <20180308073921.5c104e74@canb.auug.org.au>

On Wed, Mar 7, 2018 at 9:39 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Linus,
>
> 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?

Yours,
Linus Walleij

  reply index

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 20:39 Stephen Rothwell
2018-03-07 22:25 ` Linus Walleij [this message]
2018-03-08  0:36   ` Stephen Rothwell
2018-03-08  7:05     ` Geert Uytterhoeven
2018-03-08 12:04     ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
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 publically 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=CACRpkdaWd_7QWd7t5i6DvU3_Gu1giR9v2uoqQiLNXVWTPEty8w@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=geert+renesas@glider.be \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org linux-next@archiver.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/ public-inbox