All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: jmondi <jacopo@jmondi.org>
Cc: Simon Horman <horms@verge.net.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the renesas tree
Date: Fri, 28 Jul 2017 15:57:46 +1000	[thread overview]
Message-ID: <20170728155746.47f0f8c3@canb.auug.org.au> (raw)
In-Reply-To: <20170728050912.GB531@localhost>

Hi,

On Fri, 28 Jul 2017 12:09:12 +0700 jmondi <jacopo@jmondi.org> wrote:
>
> On Fri, Jul 28, 2017 at 09:21:08AM +1000, Stephen Rothwell wrote:
> >
> > Commit
> >
> >   bb003371172f ("arm: dts: genmai: Add RIIC2 pin group")
> >
> > is missing a Signed-off-by from its committer.  
> 
> I do see my SOB in the patch I've sent. Any chance it has been dropped
> while applying it? Should I resend?

The commit is missing Simon's Signed-off-by ...

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-07-28  5:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 23:21 linux-next: Signed-off-by missing for commit in the renesas tree Stephen Rothwell
2017-07-28  5:09 ` jmondi
2017-07-28  5:57   ` Stephen Rothwell [this message]
2017-07-28 19:56     ` Simon Horman
2017-12-20 20:01 Stephen Rothwell
2017-12-21  9:21 ` Simon Horman
2018-04-23 21:32 Stephen Rothwell
2018-07-09 21:44 Stephen Rothwell
2018-07-11  7:12 ` Simon Horman
2020-04-20 11:03 Stephen Rothwell
2020-04-20 11:13 ` Geert Uytterhoeven
2023-11-13 20:51 Stephen Rothwell
2023-11-14  7:49 ` Geert Uytterhoeven

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=20170728155746.47f0f8c3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=horms@verge.net.au \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jacopo@jmondi.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.