linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: Greg KH <gregkh@suse.de>,
	Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org, Linus Torvalds <torvalds@osdl.org>,
	paulus@samba.org
Subject: Re: Linux 2.6.20-rc4
Date: Tue, 09 Jan 2007 15:28:21 +0800	[thread overview]
Message-ID: <1168327701.14763.324.camel@shinybook.infradead.org> (raw)
In-Reply-To: <45A340E4.5030702@246tNt.com>

On Tue, 2007-01-09 at 08:14 +0100, Sylvain Munaut wrote:
> But maybe the question we should ask is why would it build
> drivers/usb/host/ohci-ppc-soc.c for an iMac G3 ... Because that problem
> (ohci multiple glue in module) is there since a long time, just never
> spotted before.

Are you suggesting that distributions must choose to support OHCI from
_either_ PCI or OF but not both?

-- 
dwmw2

  reply	other threads:[~2007-01-09  7:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0701062216210.3661@woody.osdl.org>
2007-01-08 14:50 ` Linux 2.6.20-rc4 Mariusz Kozlowski
2007-01-08 14:58   ` Sylvain Munaut
2007-01-08 15:03     ` Mariusz Kozlowski
2007-01-08 19:11     ` Jean Delvare
2007-01-09  0:38     ` Benjamin Herrenschmidt
2007-01-09  0:56       ` Greg KH
2007-01-09  2:05         ` Benjamin Herrenschmidt
2007-01-09  7:04           ` David Woodhouse
2007-01-09  7:04             ` Sylvain Munaut
2007-01-09  9:04             ` Benjamin Herrenschmidt
2007-01-09  7:14           ` Sylvain Munaut
2007-01-09  7:28             ` David Woodhouse [this message]
2007-01-09  9:08               ` Benjamin Herrenschmidt
2007-01-09  9:07             ` Benjamin Herrenschmidt
2007-01-09  7:18           ` Greg KH

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=1168327701.14763.324.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=m.kozlowski@tuxland.pl \
    --cc=paulus@samba.org \
    --cc=tnt@246tNt.com \
    --cc=torvalds@osdl.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 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).