public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Signed-off-by for RPI U-Boot USB patches
Date: Sun, 2 Feb 2014 08:05:41 +0100	[thread overview]
Message-ID: <20140202070541.GA32007@kroah.com> (raw)
In-Reply-To: <52EDE2DF.1090109@wwwdotorg.org>

On Sat, Feb 01, 2014 at 11:17:03PM -0700, Stephen Warren wrote:
> (Sorry for the spam; resending with the correct U-Boot mailing list in CC)
> 
> On 02/01/2014 11:14 PM, Stephen Warren wrote:
> > Oleksandr, I'm starting to look at getting USB support enabled for the
> > Raspberry Pi in mainline U-Boot. To that end, I looked at:
> > 
> > git://github.com/gonzoua/u-boot-pi.git rpi
> > 
> > I took the DWC driver from there and applied it to a very recent
> > mainline U-Boot. It works very well:-)
> > 
> > The main thing preventing me from sending the driver for inclusion in
> > mainline U-Boot is that none of the commits in that branch contain a
> > Signed-off-by tag from you. Could you please reply here with your s-o-b
> > line for all the commits listed below?
> > 
> > Thank you very much!
> > 
> > For details of what s-o-b means, please see
> > https://www.kernel.org/doc/Documentation/SubmittingPatches section 12
> > "Sign your work". (There's also a standalone website containing that
> > section now, but I can't for the life of me find it...)

http://developercertificate.org/ is what you are looking for.

  reply	other threads:[~2014-02-02  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52EDE25F.6080109@wwwdotorg.org>
2014-02-02  6:17 ` [U-Boot] Signed-off-by for RPI U-Boot USB patches Stephen Warren
2014-02-02  7:05   ` Greg KH [this message]
2014-02-03  4:21   ` Oleksandr Tymoshenko
2014-02-03  8:23   ` Lukasz Majewski
2014-02-03 17:03     ` Stephen Warren
2014-02-04  6:29       ` Lukasz Majewski

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=20140202070541.GA32007@kroah.com \
    --to=greg@kroah.com \
    --cc=u-boot@lists.denx.de \
    /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