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@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the pinctrl tree
Date: Tue, 10 Jul 2018 00:46:09 +0200 [thread overview]
Message-ID: <CACRpkdZrsGzULrNaoaX6bSy6z6o-gshQXrRhzUk=tuFF86shDw@mail.gmail.com> (raw)
In-Reply-To: <20180710075439.4a449b3d@canb.auug.org.au>
Hm must have come from Geert's pull request?
(I'm regularly wrong about this so not so certain...)
Geert can I fix it the usual way by simply rebasing and
adding the right SoB?
Yours,
Linus Walleij
On Mon, Jul 9, 2018 at 11:54 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Linus,
>
> Commit
>
> a742fcf72902 ("pinctrl: sh-pfc: r8a77990: Add USB3.0 pins, groups and functions")
>
> is missing a Signed-off-by from its author.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2018-07-09 22:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 21:54 linux-next: Signed-off-by missing for commit in the pinctrl tree Stephen Rothwell
2018-07-09 22:46 ` Linus Walleij [this message]
2018-07-10 1:18 ` Yoshihiro Shimoda
2018-07-10 7:07 ` Geert Uytterhoeven
-- 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-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-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='CACRpkdZrsGzULrNaoaX6bSy6z6o-gshQXrRhzUk=tuFF86shDw@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 \
--cc=takeshi.kihara.df@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).