From: Felipe Balbi <balbi@ti.com>
To: Chen Peter-B29397 <B29397@freescale.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Li Yang-R58472 <r58472@freescale.com>,
Felipe Balbi <balbi@ti.com>
Subject: Re: [BUILD BREAK] usb: gadget: fsl_mxc_udc can't compile on current v3.8-rc3
Date: Fri, 11 Jan 2013 10:27:31 +0200 [thread overview]
Message-ID: <20130111082731.GA11085@arwen.pp.htv.fi> (raw)
In-Reply-To: <F281D0F91ED19E4D8E63A7504E8A649803D63ACE@039-SN2MPN1-022.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Fri, Jan 11, 2013 at 03:23:59AM +0000, Chen Peter-B29397 wrote:
>
> > > >
> > > > Some recent patch has caused fsl_mxc_udc.c driver to fail compilation
> > > > because it can't find <mach/hardware.h> anymore.
> > > >
> > > > I would like this to be fixed still during this -rc cycle.
> > >
> > > Me too, who's sending a patch? :)
> >
> > Hi Peter,
> >
> > Who is currently working on the i.mx USB?
> >
>
> I am working on it, but there are two versions, this one and chipidea's.
>
> Anyway, I will send a patch to fix this problem.
if you're already using chipidea, then send me a patch removing this
driver and focus your effort on chipidea.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-11 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 10:08 [BUILD BREAK] usb: gadget: fsl_mxc_udc can't compile on current v3.8-rc3 Felipe Balbi
2013-01-10 14:30 ` Greg KH
2013-01-11 1:37 ` Peter Chen
2013-01-11 3:21 ` Li Yang-R58472
2013-01-11 3:23 ` Chen Peter-B29397
2013-01-11 8:27 ` Felipe Balbi [this message]
2013-01-11 8:35 ` Chen Peter-B29397
2013-01-11 8:41 ` Felipe Balbi
2013-01-11 9:24 ` Li Yang-R58472
2013-01-11 9:47 ` Felipe Balbi
2013-01-11 10:47 ` Mehresh Ramneek-B31383
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=20130111082731.GA11085@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=B29397@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r58472@freescale.com \
/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).