From: Ben Gamari <bgamari.foss@gmail.com>
To: linux-usb@vger.kernel.org
Cc: linux-omap@vger.kernel.org, balbi@ti.com,
Ajay Kumar Gupta <ajay.gupta@ti.com>
Subject: Re: [PATCH] musb: am35x: fix compile error due to control apis
Date: Thu, 23 Dec 2010 12:16:22 -0500 [thread overview]
Message-ID: <87hbe41kbd.fsf@gmail.com> (raw)
In-Reply-To: <1291399965-19623-1-git-send-email-ajay.gupta@ti.com>
On Fri, 3 Dec 2010 23:42:45 +0530, Ajay Kumar Gupta <ajay.gupta@ti.com> wrote:
> As the control.h have been moved to new location and it's
> uses are not allowed to drivers directly so moving the phy
> control, interrupt clear and reset functionality to board
> files.
>
Is this change slated to go into 2.6.37? As it stands it looks like
2.6.37 will be released with completely broken musb support on many boards
(including the BeagleBoard).
- Ben
next prev parent reply other threads:[~2010-12-23 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 18:12 [PATCH] musb: am35x: fix compile error due to control apis Ajay Kumar Gupta
[not found] ` <1291399965-19623-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2010-12-03 18:50 ` Anand Gadiyar
2010-12-04 13:53 ` Gupta, Ajay Kumar
2010-12-03 19:23 ` Sergei Shtylyov
2010-12-04 13:57 ` Gupta, Ajay Kumar
2010-12-23 17:16 ` Ben Gamari [this message]
[not found] ` <87hbe41kbd.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-27 9:20 ` Felipe Balbi
[not found] ` <20101227092038.GB2301-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2010-12-30 7:44 ` Ben Gamari
[not found] ` <877heriu1j.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-30 12:27 ` Felipe Balbi
2010-12-30 13:06 ` Sergei Shtylyov
2010-12-30 15:00 ` Ben Gamari
2010-12-30 15:24 ` Anca Emanuel
[not found] ` <AANLkTinE9Dgz9nCFv-1d=DdF22OEXSYn16s7krxo3CGp-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-30 16:04 ` Felipe Balbi
2010-12-30 16:05 ` Felipe Balbi
2010-12-30 16:14 ` Sergei Shtylyov
2010-12-30 16:20 ` Ben Gamari
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=87hbe41kbd.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=ajay.gupta@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.