From: javier.martin@vista-silicon.com (javier Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: Patches for Freescale MXC SoCs and direct ULPI communication [v3]
Date: Wed, 7 Oct 2009 08:34:38 +0200 [thread overview]
Message-ID: <eedb5540910062334h282315edi750bf10b48448163@mail.gmail.com> (raw)
In-Reply-To: <20090907102006.GB31592@pengutronix.de>
What is the status regarding to mainline about these patches?
Have they been applied somewhere?
Thanks.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091007/d74e2226/attachment.htm>
next prev parent reply other threads:[~2009-10-07 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 20:47 Patches for Freescale MXC SoCs and direct ULPI communication [v3] Daniel Mack
2009-09-02 20:47 ` [PATCH 1/5] USB OTG: add support for ulpi connected external transceivers Daniel Mack
2009-09-02 20:47 ` [PATCH 2/5] USB OTG: Add generic driver for ULPI OTG transceiver Daniel Mack
2009-09-02 20:47 ` [PATCH 3/5] MXC: Add support for ULPI Viewports Daniel Mack
2009-09-02 20:47 ` [PATCH 4/5] USB: Add EHCI support for MX27 and MX31 based boards Daniel Mack
2009-09-02 20:47 ` [PATCH 5/5] MX3: add USB support for lilly1131 Daniel Mack
2009-09-03 15:41 ` Patches for Freescale MXC SoCs and direct ULPI communication [v3] Valentin Longchamp
2009-09-07 10:20 ` s.hauer at pengutronix.de
2009-10-07 6:34 ` javier Martin [this message]
2009-10-07 6:48 ` Daniel Mack
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=eedb5540910062334h282315edi750bf10b48448163@mail.gmail.com \
--to=javier.martin@vista-silicon.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 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).