public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Yoshinori Sato <ysato@users•sourceforge.jp>
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: Wed, 18 Jul 2018 07:57:50 +1000	[thread overview]
Message-ID: <20180718075750.037fd403@canb.auug.org.au> (raw)
In-Reply-To: <87o9f6l0ck.wl-ysato@users.sourceforge.jp>

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

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.
-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2018-07-17 21:57 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 [this message]
2018-07-18 21:56     ` Yoshinori Sato

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=20180718075750.037fd403@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ysato@users$(echo .)sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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