From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Signed-off-by for RPI U-Boot USB patches
Date: Sat, 01 Feb 2014 23:17:03 -0700 [thread overview]
Message-ID: <52EDE2DF.1090109@wwwdotorg.org> (raw)
In-Reply-To: <52EDE25F.6080109@wwwdotorg.org>
(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...)
>
> b22090f Fix usb_lowlevel_init and usb_lowlevel_stop
> 8d5c624 Merge of doom: update to latest u-boot
> cd2dac2 Increase buffer for bulk transfers and make virtual hub highspeed
> fc4164b Enable USB mass storage support
> 9085155 Increase timeout for soft reset
> 4b3863c More sophysticated initialization code
> 8cb8ecc Rmeove hardcoded MAC address
> 6ab7258 Report error, do not hang
> 9e5763c Fix typo and whitespaces
> d141598 Fix memory layout for U-Boot
> 5d8b20f Cleanup and add function declarations
> eb2bb98 Add sanity check, just in case
> 8c85e48 Clean up mess with buffers
> d8fb4c3 Get rid of device-specific structures/registers
> ce7f827 Merge branch 'rpi' of github.com:gonzoua/u-boot-pi into rpi
> a78f29e Slap licenses on top of the newly created files
> d80dd6a Remove debug level
> cc7227e Minor cleanup
> 0d3c12f More stable CONTROL transfers, working BULK transfers
> 9da26b0 Remove debug output
> 70f4b54 Add support for USB ethernet and SMSC95XX
> ae9e5fc Add stripped-down version of Linux driver for DWC OTG
> a1bfc20 Skeleton DWC OTG driver implementation
> b47e41c Slap licenses on top of the newly created files
> ded1dc9 Remove debug level
> 602704e Minor cleanup
> ecc6e3d More stable CONTROL transfers, working BULK transfers
> d966ac2 Add support for USB ethernet and SMSC95XX
> 71633e5 Add stripped-down version of Linux driver for DWC OTG
> 182c5b0 Skeleton DWC OTG driver implementation
>
> (yes, there are duplicate entries in that list, because there are in the
> git tree I took the code from)
>
> _______________________________________________
> linux-rpi-kernel mailing list
> linux-rpi-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rpi-kernel
>
next parent reply other threads:[~2014-02-02 6:17 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 ` Stephen Warren [this message]
2014-02-02 7:05 ` [U-Boot] Signed-off-by for RPI U-Boot USB patches Greg KH
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=52EDE2DF.1090109@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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