From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: USB PHY documentation
Date: Fri, 26 Aug 2016 12:45:45 +0200 [thread overview]
Message-ID: <CAFBinCCx4X_Lsd9NsFd-9aHL67EvCJDebdzc8zdSP9Hcw__BOA@mail.gmail.com> (raw)
In-Reply-To: <1472029412.2322.13.camel@baylibre.com>
On Wed, Aug 24, 2016 at 11:03 AM, jbrunet <jbrunet@baylibre.com> wrote:
> I'm still checking the otg controller.
I've seen that you made more changes in your github repo.
Maybe you could give me/us an update before your leave today so I can
continue where you left tonight/tomorrow.
How should we proceed with signed-off-by in these patches?
We have both written/changed a part of it, should we both simply add
our own SOB to the patches?
next prev parent reply other threads:[~2016-08-26 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 21:39 USB PHY documentation Martin Blumenstingl
2016-08-23 13:30 ` Ben Dooks
2016-08-24 9:03 ` jbrunet
2016-08-24 10:19 ` Martin Blumenstingl
2016-08-26 10:45 ` Martin Blumenstingl [this message]
[not found] ` <CAO9vn2P8vPwFFpz-VN3WKV_BNhwXWW=NkjTEhoGvYShbrZMwsA@mail.gmail.com>
2016-08-27 21:32 ` Martin Blumenstingl
2016-08-28 16:25 ` Martin Blumenstingl
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=CAFBinCCx4X_Lsd9NsFd-9aHL67EvCJDebdzc8zdSP9Hcw__BOA@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linus-amlogic@lists.infradead.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).