linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: John Linville <linville@tuxdriver.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	linux-wireless@vger.kernel.org,
	Gary Zambrano <zambrano@broadcom.com>
Subject: Re: [patch 2/2] ssb: Add a driver for the Broadcom OHCI core
Date: Thu, 12 Jul 2007 22:57:56 +0200	[thread overview]
Message-ID: <200707122257.56526.mb@bu3sch.de> (raw)
In-Reply-To: <20070712104937.1b0970c5.akpm@linux-foundation.org>

On Thursday 12 July 2007 19:49, Andrew Morton wrote:
> Here, we'd normally do
> 
> #else
> #define ssb_ohci_hcd_suspend NULL
> #define ssb_ohci_hcd_resume NULL

Ah, well. I don't care either way, so if that is the preferred way to deal
with it, I'll change :)

> > Index: linux-2.6/drivers/usb/host/ohci-hcd.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/usb/host/ohci-hcd.c	2007-07-12 10:51:46.000000000 +0200
> > +++ linux-2.6/drivers/usb/host/ohci-hcd.c	2007-07-12 10:52:45.000000000 +0200
> > @@ -920,11 +920,17 @@ MODULE_LICENSE ("GPL");
> >  #define PS3_SYSTEM_BUS_DRIVER	ps3_ohci_sb_driver
> >  #endif
> >  
> > +#ifdef CONFIG_USB_OHCI_HCD_SSB
> > +#include "ohci-ssb.c"
> > +#define SSB_OHCI_DRIVER		ssb_ohci_driver
> > +#endif
> 
> argh.  Why did USB do this?  Sigh.
> 
> >  #if	!defined(PCI_DRIVER) &&		\
> >  	!defined(PLATFORM_DRIVER) &&	\
> >  	!defined(OF_PLATFORM_DRIVER) &&	\
> >  	!defined(SA1111_DRIVER) &&	\
> > -	!defined(PS3_SYSTEM_BUS_DRIVER)
> > +	!defined(PS3_SYSTEM_BUS_DRIVER) && \
> > +	!defined(SSB_OHCI_DRIVER)
> >  #error "missing bus glue for ohci-hcd"
> >  #endif
> >  
> > @@ -972,10 +978,20 @@ static int __init ohci_hcd_mod_init(void
> >  		goto error_pci;
> >  #endif
> >  
> > +#ifdef SSB_OHCI_DRIVER
> > +	retval = ssb_driver_register(&SSB_OHCI_DRIVER);
> > +	if (retval)
> > +		goto error_ssb;
> > +#endif
> 
> Why do we use SSB_OHCI_DRIVER here rather than ssb_ohci_driver?   Seems odd.

Yes, that ohci code is horrible. But all other ohci drivers do it this way, too,
so I did it, too.

> > +
> >  	return retval;
> >  
> >  	/* Error path */
> > +#ifdef SSB_OHCI_DRIVER
> > + error_ssb:
> > +#endif
> >  #ifdef PCI_DRIVER
> > +	pci_unregister_driver(&PCI_DRIVER);
> 
> hm, are you sure about this?  I don't see anywhere in here where PCI_DRIVER
> got newly registered, but we are newly unregistering it?

Whoops, good catch. That's a merge error.

  reply	other threads:[~2007-07-12 20:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  8:54 [patch 0/2] Merge the SSB subsystem mb
2007-07-12  8:54 ` [patch 2/2] ssb: Add a driver for the Broadcom OHCI core mb
2007-07-12 16:04   ` Randy Dunlap
2007-07-12 16:08     ` Greg KH
2007-07-12 17:49   ` Andrew Morton
2007-07-12 20:57     ` Michael Buesch [this message]
     [not found] ` <20070712085744.604965000@bu3sch.de>
2007-07-12 18:27   ` [patch 1/2] Merge the Sonics Silicon Backplane subsystem Andrew Morton
2007-07-12 21:42     ` Michael Buesch
2007-07-12 21:53       ` Andrew Morton
2007-07-12 22:10         ` Michael Buesch
2007-07-12 22:25           ` Andrew Morton
2007-07-13  6:11   ` Aurelien Jarno
2007-07-13  7:09     ` Holger Schurig
2007-07-13 10:22     ` Michael Buesch

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=200707122257.56526.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=akpm@linux-foundation.org \
    --cc=aurelien@aurel32.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=zambrano@broadcom.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).