From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 commits in the h8300 tree
Date: Thu, 19 Jul 2018 06:56:13 +0900 [thread overview]
Message-ID: <877els439e.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20180718075750.037fd403@canb.auug.org.au>
On Wed, 18 Jul 2018 06:57:50 +0900,
Stephen Rothwell wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> Hi Yoshinori,
>
> On Tue, 17 Jul 2018 17:42:35 +0900 Yoshinori Sato <ysato@users.sourceforge.jp> wrote:
> >
> > On Tue, 17 Jul 2018 04:24:19 +0900, Stephen Rothwell wrote:
> > >
> > > Commit
> > >
> > > 39f077046d46 ("h8300: switch to NO_BOOTMEM")
> > >
> > > is missing a Signed-off-by from its committer.
> > >
> > > Commits
> > >
> > > d6bde68ad18e ("h8300: Add missing output register.")
> > > 5aa2f1573e0c ("h8300: gcc-8.1 fix")
> > >
> > > are missing a Signed-off-by from their author and committer.
> >
> > OK. Fixed.
>
> Not really, you now have those patches in your tree twice :-( To fix
> the missing SOB lines you really needed to rewrite your branch without
> the original commits above.
Oh sorry.
I think that I will be fine this time.
--
> Cheers,
> Stephen Rothwell
> [2 OpenPGP digital signature <application/pgp-signature (7bit)>]
> No public key for 015042F34957D06C created at 2018-07-18T06:57:50+0900 using RSA
--
Yosinori Sato
prev parent reply other threads:[~2018-07-18 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 19:24 linux-next: Signed-off-by missing for commits in the h8300 tree Stephen Rothwell
2018-07-17 8:42 ` Yoshinori Sato
2018-07-17 21:57 ` Stephen Rothwell
2018-07-18 21:56 ` Yoshinori Sato [this message]
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=877els439e.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--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.