From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [UBOOT] [PATCH v2 0/4] DWC back port from Linux kernel
Date: Mon, 1 Jul 2013 13:04:25 +0200 [thread overview]
Message-ID: <201307011304.25335.marex@denx.de> (raw)
In-Reply-To: <1372092235-15163-1-git-send-email-dmurphy@ti.com>
Dear Dan Murphy,
> This patch series has been generated in an effort to get comments on
> the implementation of the dwc code within the uBoot.
>
> V2 incorporates comments to first port the kernel header backward to uBoot
> and then produce the uBoot changes so the uBoot changes are easily
> distinguishable from the original kernel source.
>
> The first patch is the one of major concern as this patch will make an
> attempt to commonize the usb headers so that there is re-use and prepare
> the usb headers for future usb code back ports from the linux kernel.
>
> This code will compile for omap5 and omap4 but fails for am335x.
> Before I invest anymore time in this I would like to understand if there
> are any comments on the overall implemenation.
Ok, the code is nicely contained and can be easily resynced with mainline.
Please continue and sorry for the long delay.
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-07-01 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 16:43 [U-Boot] [RFC] [UBOOT] [PATCH v2 0/4] DWC back port from Linux kernel Dan Murphy
2013-06-24 16:43 ` [U-Boot] [RFC] [UBOOT] [PATCH v2 1/4] USB: Backport kernel usb header file Dan Murphy
2013-06-24 16:43 ` [U-Boot] [RFC] [UBOOT] [PATCH v2 2/4] USB: Adapt the usb-compat.h to uboot and fix compiler errors Dan Murphy
2013-06-24 20:16 ` Tom Rini
2013-07-01 10:56 ` Marek Vasut
2013-06-24 16:43 ` [U-Boot] [RFC] [UBOOT] [PATCH v2 3/4] USB: dwc3: Initial back port of dwc3 code Dan Murphy
2013-06-25 11:19 ` Roger Quadros
2013-06-24 16:43 ` [U-Boot] [RFC] [UBOOT] [PATCH v2 4/4] omap5: usb: Add usb otg clocks and enable Dan Murphy
2013-07-01 11:04 ` Marek Vasut [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=201307011304.25335.marex@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