linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sagar Dharia <sdharia@codeaurora.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the char-misc tree
Date: Wed, 20 Dec 2017 18:22:49 +0100	[thread overview]
Message-ID: <20171220172249.GA5736@kroah.com> (raw)
In-Reply-To: <6bb2f803-daa2-6b7a-b5a6-9d8037726d12@linaro.org>

On Wed, Dec 20, 2017 at 12:38:43PM +0000, Srinivas Kandagatla wrote:
> Hi Greg,
> 
> On 20/12/17 09:41, Greg KH wrote:
> > On Wed, Dec 20, 2017 at 07:12:16AM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > Commits
> > > 
> > >    46a2bb5a7f7e ("slimbus: core: Add slim controllers support")
> > >    afbdcc7c384b ("slimbus: Add messaging APIs to slimbus framework")
> > > 
> > > are missing a Signed-off-by from their author.
> Sorry about this!
> 
> > 
> > I am guessing that Linaro doesn't know about the codeveloped-by new tag
> > here :(
> > 
> Do you want me to resend the series with missing Signed-off or
> Codeveloped-by tags?

It's ok, I have at least one signed-off-by on these from someone I can
go kick if something goes wrong :)

thanks,

greg k-h

      reply	other threads:[~2017-12-20 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 20:12 linux-next: Signed-off-by missing for commits in the char-misc tree Stephen Rothwell
2017-12-20  9:41 ` Greg KH
2017-12-20  9:55   ` Mark Brown
2017-12-20 10:02     ` Greg KH
2017-12-20 12:38   ` Srinivas Kandagatla
2017-12-20 17:22     ` Greg KH [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=20171220172249.GA5736@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sdharia@codeaurora.org \
    --cc=sfr@canb.auug.org.au \
    --cc=srinivas.kandagatla@linaro.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 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).