From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] drivers: usb: common: add common code for usb drivers to use
Date: Wed, 13 Apr 2016 13:47:19 +0200 [thread overview]
Message-ID: <570E31C7.4060100@denx.de> (raw)
In-Reply-To: <CAPnjgZ2S=g7-bAF_PCV=KYhZh-Fm=vVcymepsTmhOggxZKg8Zg@mail.gmail.com>
On 04/13/2016 01:19 PM, Simon Glass wrote:
> On 12 April 2016 at 04:31, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>> Add common usb code which usb drivers makes use of it.
>>
>> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
>> ---
>>
>> This was in my musb dm bringup patch list, and I did dwc3 over
>> the same branch so missed submitting this patch for dwc3 bringup.
>> So submitting the dwc3 dependent patch separately and will drop
>> this while submitting v2 for musb.
>>
>> Simon, before applying [1], can you apply this first so that the
>> dependents are met.
>>
>> [1]: https://www.mail-archive.com/u-boot at lists.denx.de/msg206602.html
>>
>> ---
>> Makefile | 1 +
>> drivers/usb/common/Makefile | 8 ++++++++
>> drivers/usb/common/common.c | 40 ++++++++++++++++++++++++++++++++++++++++
>> include/linux/usb/otg.h | 9 +++++++++
>> 4 files changed, 58 insertions(+)
>> create mode 100644 drivers/usb/common/Makefile
>> create mode 100644 drivers/usb/common/common.c
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> Marek, if you are OK with it, i'd like to bring this into u-boot-dm as
> it is a prerequisite for a series in my patchwork todo list.
That's fine, thanks.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-04-13 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 10:31 [U-Boot] [PATCH 1/1] drivers: usb: common: add common code for usb drivers to use Mugunthan V N
2016-04-13 11:19 ` Simon Glass
2016-04-13 11:47 ` Marek Vasut [this message]
2016-05-07 19:03 ` Simon Glass
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=570E31C7.4060100@denx.de \
--to=marex@denx.de \
--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