From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Svetoslav Neykov <svetoslav@neykov.name>,
'Ralf Baechle' <ralf@linux-mips.org>,
'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>,
'Gabor Juhos' <juhosg@openwrt.org>,
'John Crispin' <blogic@openwrt.org>,
'Alan Stern' <stern@rowland.harvard.edu>,
"'Luis R. Rodriguez'" <mcgrof@qca.qualcomm.com>,
linux-mips@linux-mips.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/5] Chipidea driver support for the AR933x platform
Date: Tue, 26 Feb 2013 16:45:23 +0100 [thread overview]
Message-ID: <512CD893.50904@pengutronix.de> (raw)
In-Reply-To: <878v6bxhbd.fsf@ashishki-desk.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On 02/26/2013 03:47 PM, Alexander Shishkin wrote:
> Svetoslav Neykov <svetoslav@neykov.name> writes:
>
>> Hi Alex,
>> I am working on the incorporating all received comments - thanks to all for
>> taking their time to comment.
>> Apologies for not replying to the received mails, didn't want to spam with
>> OK replies to each separately.
>
> Great, thanks!
> Looks like this patchset will need some synchronization with Sacha's
> dr_mode/phy_mode patchset, but I presume you're aware of that.
The current version of Sascha's patches is here:
http://git.pengutronix.de/?p=mgr/linux.git;a=shortlog;h=refs/heads/chipidea-for-v3.10
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-02-26 15:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 21:38 [PATCH 0/5] Chipidea driver support for the AR933x platform Svetoslav Neykov
2013-02-13 21:38 ` [PATCH 1/5] usb: chipidea: big-endian support Svetoslav Neykov
2013-02-13 21:38 ` [PATCH 2/5] usb: chipidea: flags to force usb mode (host/device) Svetoslav Neykov
2013-02-14 9:01 ` Michael Grzeschik
2013-02-13 21:38 ` [PATCH 3/5] usb: chipidea: Don't access OTG related registers Svetoslav Neykov
2013-02-14 11:45 ` Alexander Shishkin
2013-02-14 11:45 ` Alexander Shishkin
2013-02-13 21:38 ` [PATCH 4/5] usb: chipidea: AR933x platform support for the chipidea driver Svetoslav Neykov
2013-02-14 11:23 ` Alexander Shishkin
2013-02-14 11:23 ` Alexander Shishkin
2013-02-14 14:19 ` Gabor Juhos
2013-02-13 21:38 ` [PATCH 5/5] usb: chipidea: Fix incorrect check of function return value Svetoslav Neykov
2013-02-14 11:08 ` Alexander Shishkin
2013-02-14 11:08 ` Alexander Shishkin
2013-02-26 13:35 ` [PATCH 0/5] Chipidea driver support for the AR933x platform Alexander Shishkin
2013-02-26 13:35 ` Alexander Shishkin
2013-02-26 14:38 ` Svetoslav Neykov
2013-02-26 14:38 ` Svetoslav Neykov
2013-02-26 14:47 ` Alexander Shishkin
2013-02-26 14:54 ` Svetoslav Neykov
2013-02-26 14:54 ` Svetoslav Neykov
2013-02-26 15:45 ` Marc Kleine-Budde [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=512CD893.50904@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=blogic@openwrt.org \
--cc=gregkh@linuxfoundation.org \
--cc=juhosg@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=ralf@linux-mips.org \
--cc=stern@rowland.harvard.edu \
--cc=svetoslav@neykov.name \
/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