From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Hiroo Matsumoto <matsumoto.hiroo@jp.fujitsu.com>,
Michal Simek <monstr@monstr.eu>,
microblaze-uclinux@itee.uq.edu.au, linux-pci@vger.kernel.org,
Jesse Larrew <jlarrew@linux.vnet.ibm.com>,
jbarnes@virtuousgeek.org,
Dominik Brodowski <linux@dominikbrodowski.net>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 1/2] powerpc/PCI: move DMA & IRQ init to device_add() notification path
Date: Fri, 25 May 2012 13:38:25 +1000 [thread overview]
Message-ID: <1337917105.16119.11.camel@pasglop> (raw)
In-Reply-To: <CAErSpo6W28r4f5pJmZr=ofUAaffiUtOqgXWeabGpr+DmKw+Z+g@mail.gmail.com>
On Thu, 2012-05-24 at 21:08 -0600, Bjorn Helgaas wrote:
>
> OK. Are you worried about cardbus in particular?
>
> This is headed for the 3.6, not 3.5, so we should have plenty of time.
> As soon as everything for the current merge window gets merged and
> -next is ready for the next batch, I'll put this in there.
I'm not that worried about cardbus ... in fact I wouldn't be surprised
if it's already somewhat broken, I haven't tested it in a long time...
I'm more worried about basic functionality and expectations about when
things happen during boot vs. platform hacks, that and pseries specific
kind of hotplug which can be a bit odd.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Michal Simek <monstr@monstr.eu>,
Hiroo Matsumoto <matsumoto.hiroo@jp.fujitsu.com>,
microblaze-uclinux@itee.uq.edu.au,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Jesse Larrew <jlarrew@linux.vnet.ibm.com>,
jbarnes@virtuousgeek.org,
Dominik Brodowski <linux@dominikbrodowski.net>,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 1/2] powerpc/PCI: move DMA & IRQ init to device_add() notification path
Date: Fri, 25 May 2012 13:38:25 +1000 [thread overview]
Message-ID: <1337917105.16119.11.camel@pasglop> (raw)
In-Reply-To: <CAErSpo6W28r4f5pJmZr=ofUAaffiUtOqgXWeabGpr+DmKw+Z+g@mail.gmail.com>
On Thu, 2012-05-24 at 21:08 -0600, Bjorn Helgaas wrote:
>
> OK. Are you worried about cardbus in particular?
>
> This is headed for the 3.6, not 3.5, so we should have plenty of time.
> As soon as everything for the current merge window gets merged and
> -next is ready for the next batch, I'll put this in there.
I'm not that worried about cardbus ... in fact I wouldn't be surprised
if it's already somewhat broken, I haven't tested it in a long time...
I'm more worried about basic functionality and expectations about when
things happen during boot vs. platform hacks, that and pseries specific
kind of hotplug which can be a bit odd.
Cheers,
Ben.
next prev parent reply other threads:[~2012-05-25 3:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 22:36 [PATCH v3 0/2] archdata init in device_add() notifier Bjorn Helgaas
2012-05-23 22:36 ` Bjorn Helgaas
2012-05-23 22:37 ` [PATCH v3 1/2] powerpc/PCI: move DMA & IRQ init to device_add() notification path Bjorn Helgaas
2012-05-23 22:37 ` Bjorn Helgaas
2012-05-25 3:00 ` Benjamin Herrenschmidt
2012-05-25 3:00 ` Benjamin Herrenschmidt
2012-05-25 3:08 ` Bjorn Helgaas
2012-05-25 3:08 ` Bjorn Helgaas
2012-05-25 3:38 ` Benjamin Herrenschmidt [this message]
2012-05-25 3:38 ` Benjamin Herrenschmidt
2012-06-07 12:58 ` Hiroo Matsumoto
2012-06-07 12:58 ` Hiroo Matsumoto
2012-06-18 21:06 ` Bjorn Helgaas
2012-06-18 21:06 ` Bjorn Helgaas
2012-06-18 22:55 ` Benjamin Herrenschmidt
2012-06-18 22:55 ` Benjamin Herrenschmidt
2012-10-12 18:03 ` Bjorn Helgaas
2012-10-12 18:03 ` Bjorn Helgaas
2012-05-23 22:37 ` [PATCH v3 2/2] microblaze/PCI: " Bjorn Helgaas
2012-05-23 22:37 ` Bjorn Helgaas
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=1337917105.16119.11.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jlarrew@linux.vnet.ibm.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matsumoto.hiroo@jp.fujitsu.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
/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.