From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] omap3: cm-t3517: add support for usb host.
Date: Mon, 27 Sep 2010 15:28:17 -0700 [thread overview]
Message-ID: <20100927222817.GF16721@atomide.com> (raw)
In-Reply-To: <4C99BD55.3070706@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [100922 01:16]:
>
> > It should be okay to execute this code independent of whether
> > the driver is built or not. The device registration can be unconditional
> > and if there is no driver present, we won't probe anyway.
The current patch looks OK to me, adding all of them into omap-for-linus.
Regards,
Tony
next prev parent reply other threads:[~2010-09-27 22:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 16:03 [PATCH 0/5] Support for CompuLab CM-T3517 modules Igor Grinberg
2010-09-21 16:03 ` [PATCH 1/5] omap3: Introduce CompuLab CM-T3517 module Igor Grinberg
2010-09-21 16:03 ` [PATCH 2/5] omap3: cm-t3517: add support for v3020 rtc Igor Grinberg
2010-09-21 16:03 ` [PATCH 3/5] omap3: cm-t3517: add support for usb host Igor Grinberg
2010-09-21 16:26 ` Gadiyar, Anand
2010-09-22 8:24 ` Igor Grinberg
2010-09-27 22:28 ` Tony Lindgren [this message]
2010-09-21 16:03 ` [PATCH 4/5] omap3: cm-t3517: add support for NAND flash Igor Grinberg
2010-09-21 16:03 ` [PATCH 5/5] omap3: cm-t3517: add support for TI HECC Igor Grinberg
-- strict thread matches above, loose matches on Subject: below --
2010-09-16 8:54 [PATCH 0/5] Support for CompuLab CM-T3517 modules Igor Grinberg
2010-09-16 8:54 ` [PATCH 3/5] omap3: cm-t3517: add support for usb host Igor Grinberg
2010-09-16 9:00 ` Felipe Balbi
2010-09-16 9:12 ` Igor Grinberg
2010-09-16 17:48 ` Tony Lindgren
2010-09-19 9:00 ` Igor Grinberg
2010-09-20 6:39 ` Felipe Balbi
2010-09-20 14:46 ` Igor Grinberg
2010-09-21 7:07 ` Felipe Balbi
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=20100927222817.GF16721@atomide.com \
--to=tony@atomide.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).