From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org, David Brownell <david-b@pacbell.net>,
Felipe Balbi <felipe.balbi@nokia.com>,
Vikram Pandita <vikram.pandita@ti.com>,
Nishant Kamat <nskamat@ti.com>
Subject: Re: Git tree updated to v2.6.27-rc5, some USB diffs still lurking
Date: Wed, 3 Sep 2008 16:52:25 -0700 [thread overview]
Message-ID: <20080903235223.GI23085@atomide.com> (raw)
In-Reply-To: <20080903232754.GR19980@flint.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [080903 16:28]:
> On Wed, Sep 03, 2008 at 03:12:19PM -0700, Tony Lindgren wrote:
> > @@ -2687,7 +2696,7 @@
> > udc->gadget.name = driver_name;
> >
> > device_initialize(&udc->gadget.dev);
> > - dev_set_name(&udc->gadget.dev, "gadget");
> > + strcpy (udc->gadget.dev.bus_id, "gadget");
>
> FWIW, this one looks like a mismerge with the change converting direct
> accesses to dev.bus_id to use accessors.
OK thanks, fixed in l-o tree to use dev_set_name like mainline kernel
does.
> > +MODULE_ALIAS("omap-ehci");
> > +static struct platform_driver ehci_hcd_omap_driver = {
> > + .probe = ehci_hcd_omap_drv_probe,
> > + .remove = ehci_hcd_omap_drv_remove,
> > + .shutdown = usb_hcd_platform_shutdown,
> > + /*.suspend = ehci_hcd_omap_drv_suspend, */
> > + /*.resume = ehci_hcd_omap_drv_resume, */
> > + .driver = {
> > + .name = "ehci-omap",
> > + .bus = &platform_bus_type
>
> No need to set .bus.
>
> > +#ifndef __EHCI_OMAP_H
> > +#define __EHCI_OMAP_H
> > +
> > +#include <mach/hardware.h>
> > +#include "../../../arch/arm/mach-omap2/cm.h"
> > +#include "../../../arch/arm/mach-omap2/cm-regbits-34xx.h"
>
> Such includes need to die.
>
> > +#define OMAP_USBHOST_TLL_BASE (OMAP_USBHOST_BASE + 0x2000)
> > +#define OMAP_USBTLL_REVISION (OMAP_USBHOST_TLL_BASE + 0x00)
> > +#define OMAP_USBTLL_SYSCONFIG (OMAP_USBHOST_TLL_BASE + 0x10)
> > + #define OMAP_USBTLL_SYSCONFIG_CACTIVITY_SHIFT 8
> > + #define OMAP_USBTLL_SYSCONFIG_SIDLEMODE_SHIFT 3
>
> And, fyi, gcc may currently accept this, but I seem to remember that
> the C standard doesn't permit this - the '#' should always be in
> column 0, optionally followed by white space before the directive.
Vikram & Nishant, can you please fix the above comments for your echi-omap
patch for linux-usb?
> > +#include <mach/memory.h>
>
> Should be asm/memory.h (same for all other occurances.)
>
> And some of these asm/arch/ -> mach/ conversions look like missed stuff
> from the includes move, so should be a high priority to get into the
> next -rc. Tony: please sort out a patch and put it in my patch system
> for these.
OK, fixed for l-o tree. Felipe has the include fixes patch in Greg's
queue, but looks like that needs updating too. Felipe, can you take
care of that?
Thanks,
Tony
next prev parent reply other threads:[~2008-09-03 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 22:12 Git tree updated to v2.6.27-rc5, some USB diffs still lurking Tony Lindgren
2008-09-03 22:18 ` Felipe Balbi
2008-09-03 22:22 ` Tony Lindgren
2008-09-03 23:27 ` Russell King - ARM Linux
2008-09-03 23:52 ` Tony Lindgren [this message]
2008-09-03 23:55 ` Felipe Balbi
2008-09-04 0:22 ` Måns Rullgård
2008-09-04 23:20 ` David Brownell
2008-09-05 1:00 ` Tony Lindgren
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=20080903235223.GI23085@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nskamat@ti.com \
--cc=vikram.pandita@ti.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