All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Gamari <bgamari.foss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	balbi-l0cyMroinI0@public.gmane.org,
	Ajay Kumar Gupta <ajay.gupta-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v2] musb: am35x: fix compile error due to control apis
Date: Tue, 18 Jan 2011 14:15:13 -0500	[thread overview]
Message-ID: <87fwsqm3b2.fsf@gmail.com> (raw)
In-Reply-To: <1291623211-959-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>

On Mon,  6 Dec 2010 13:43:31 +0530, Ajay Kumar Gupta <ajay.gupta-l0cyMroinI0@public.gmane.org> 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.
> 
What happened to the board changes for board-am3517evm? This patch
_really_ needs to include the necessary changes to a board. So far this
change has already been handled very sloppily (i.e. 2.6.37 was released
with am35x support that doesn't even build, much less function). If we
continue with this patch as proposed, not only will board maintainers
have absolutely no idea why USB isn't working in 2.6.38, but once they
are lucky enough to stumble upon the reason they will have no idea how
to fix the problem, having no template to work from.

As I understand it, this patch has already been merged into mmotm. Can
we please get a new version of this patch or even just a patch on top of
this modifying one of the boards to accomodate this change so that the
rest of us have some idea how to proceed?

Thanks,

- Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-01-18 19:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06  8:13 [PATCH v2] musb: am35x: fix compile error due to control apis Ajay Kumar Gupta
     [not found] ` <1291623211-959-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2010-12-06 10:37   ` Sergei Shtylyov
     [not found]     ` <4CFCBCF1.9010902-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-06 12:31       ` Gupta, Ajay Kumar
2010-12-06 17:13         ` Sergei Shtylyov
2010-12-06 17:54           ` Tony Lindgren
     [not found]             ` <20101206175445.GF8345-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-12-07 13:20               ` Sergei Shtylyov
     [not found]                 ` <4CFE3495.5090204-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-15  3:01                   ` Paul Walmsley
2011-01-18 19:15   ` Ben Gamari [this message]
2011-01-24 15:45     ` Ben Gamari
     [not found]       ` <87k4hu8fvx.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-01-27  4:48         ` Felipe Balbi
     [not found]           ` <20110127044810.GJ2429-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-01-27 12:31             ` Ben Gamari
2011-02-01  7:26               ` 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=87fwsqm3b2.fsf@gmail.com \
    --to=bgamari.foss-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ajay.gupta-l0cyMroinI0@public.gmane.org \
    --cc=balbi-l0cyMroinI0@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.