From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/9] Reorganize R8A7779/Marzen USB code
Date: Fri, 12 Apr 2013 23:11:04 +0000 [thread overview]
Message-ID: <51689488.7040109@cogentembedded.com> (raw)
In-Reply-To: <51689399.5090203@cogentembedded.com>
On 04/13/2013 03:07 AM, I wrote:
>
>>
>>>> Please add this "tested on xxx" comment on each patch's log area,
>>>> not only on [0/x].
>>>> We need it on "git log"
>>> I'm going to post R8A7778/BOCK-W series following this one, and
>>> all the
>>> patches in 1st series should additionally be tested on BOCK-W. Well, I
>>> probably can hold up posting version 3 until I have the second
>>> series verified.
>>> BTW, about R8A7778/BOCK-W, R-Car M1A user manual talks about a
>>> ferrite
>>> bead in 49.4.1 (3) Setting USB-PHY. Do you know for sure if it's
>>> used or not
>>> on BOCK-W board? PHY initialization seems to work with either
>>> settings...
>> I can ask it to HW team if you want me.
Yes, ask them please.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] Reorganize R8A7779/Marzen USB code
Date: Sat, 13 Apr 2013 03:11:04 +0400 [thread overview]
Message-ID: <51689488.7040109@cogentembedded.com> (raw)
In-Reply-To: <51689399.5090203@cogentembedded.com>
On 04/13/2013 03:07 AM, I wrote:
>
>>
>>>> Please add this "tested on xxx" comment on each patch's log area,
>>>> not only on [0/x].
>>>> We need it on "git log"
>>> I'm going to post R8A7778/BOCK-W series following this one, and
>>> all the
>>> patches in 1st series should additionally be tested on BOCK-W. Well, I
>>> probably can hold up posting version 3 until I have the second
>>> series verified.
>>> BTW, about R8A7778/BOCK-W, R-Car M1A user manual talks about a
>>> ferrite
>>> bead in 49.4.1 (3) Setting USB-PHY. Do you know for sure if it's
>>> used or not
>>> on BOCK-W board? PHY initialization seems to work with either
>>> settings...
>> I can ask it to HW team if you want me.
Yes, ask them please.
WBR, Sergei
next prev parent reply other threads:[~2013-04-12 23:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 21:10 [PATCH v2 0/9] Reorganize R8A7779/Marzen USB code Sergei Shtylyov
2013-04-08 21:10 ` Sergei Shtylyov
2013-04-09 5:58 ` Kuninori Morimoto
2013-04-09 5:58 ` Kuninori Morimoto
2013-04-09 12:44 ` Sergei Shtylyov
2013-04-09 12:44 ` Sergei Shtylyov
2013-04-10 1:31 ` Kuninori Morimoto
2013-04-10 1:31 ` Kuninori Morimoto
2013-04-12 23:07 ` Sergei Shtylyov
2013-04-12 23:07 ` Sergei Shtylyov
2013-04-12 23:11 ` Sergei Shtylyov [this message]
2013-04-12 23:11 ` Sergei Shtylyov
2013-04-17 1:14 ` Kuninori Morimoto
2013-04-17 1:14 ` Kuninori Morimoto
2013-04-19 0:27 ` Kuninori Morimoto
2013-04-19 0:27 ` Kuninori Morimoto
2013-04-19 17:54 ` Sergei Shtylyov
2013-04-19 17:54 ` Sergei Shtylyov
2013-04-09 8:32 ` Simon Horman
2013-04-09 8:32 ` Simon Horman
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=51689488.7040109@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@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 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.