From: Roger Quadros <rogerq@ti.com>
To: Peter Chen <hzpeterchen@gmail.com>
Cc: <Peter.Chen@nxp.com>, <balbi@kernel.org>,
<gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] usb: otg-fsm: Add documentation and some trivial cleanups
Date: Thu, 31 Mar 2016 12:40:22 +0300 [thread overview]
Message-ID: <56FCF086.1080204@ti.com> (raw)
In-Reply-To: <20160331070825.GB3799@peterchendt>
Peter,
On 31/03/16 10:08, Peter Chen wrote:
> On Wed, Mar 30, 2016 at 12:56:27PM +0300, Roger Quadros wrote:
>> Hi,
>>
>> Add documentation for struct otg_fsm with some trivial cleanups.
>> All patches have been Acked by otg-fsm maintainer (Peter Chen).
>>
>
> I will queue them, thanks.
>
Patch 3 might cause a build failure for drivers/usb/phy/phy-fsl-usb.c
since it relies on VDBG that was defined in include/linux/usb/otg-fsm.h
I will send a revised patch 3 that locally defines VDBG for phy-fsl-usb.c
cheers,
-roger
prev parent reply other threads:[~2016-03-31 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 9:56 [PATCH v6 0/3] usb: otg-fsm: Add documentation and some trivial cleanups Roger Quadros
2016-03-30 9:56 ` [PATCH v6 1/3] usb: otg-fsm: Add documentation for struct otg_fsm Roger Quadros
2016-03-30 9:56 ` [PATCH v6 2/3] usb: otg-fsm: support multiple instances Roger Quadros
2016-03-30 9:56 ` [PATCH v6 3/3] usb: otg-fsm: Prevent build warning "VDBG" redefined Roger Quadros
2016-03-31 9:41 ` [PATCH v7 " Roger Quadros
2016-04-05 8:52 ` Peter Chen
2016-04-05 12:52 ` Roger Quadros
2016-04-05 13:48 ` Roger Quadros
2016-04-06 6:46 ` Peter Chen
2016-04-06 7:13 ` Roger Quadros
2016-04-19 8:21 ` Peter Chen
2016-03-31 7:08 ` [PATCH v6 0/3] usb: otg-fsm: Add documentation and some trivial cleanups Peter Chen
2016-03-31 9:40 ` Roger Quadros [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=56FCF086.1080204@ti.com \
--to=rogerq@ti.com \
--cc=Peter.Chen@nxp.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hzpeterchen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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