From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mark Takatz <takatz@pericle.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: use generic pci_assign_unassign_resources
Date: Mon, 16 Mar 2009 10:56:54 +1100 [thread overview]
Message-ID: <1237161414.25062.105.camel@pasglop> (raw)
In-Reply-To: <49BAE147.4060102@pericle.com>
On Fri, 2009-03-13 at 16:42 -0600, Mark Takatz wrote:
> Ben,
>
> We're looking at the fixes you put in place for the various PCI errors
> and we think this is the solution we need for our system, a GE Fanuc CM6
> PPC board (single 8641), but your patches appear to apply either to
> 2.6.24 or 2.6.25, and we have 2.6.23. Do you know of any similar work
> done on the 2.6.23 release?
>
> Thanks in advance for any help you can provide,
No, you would have to backport major chunks of the PCI rework I did in
between, along with fixes I did after that. At this stage I would
recommend considering an update to 2.6.27 or 2.6.28.
Cheers,
Ben.
next prev parent reply other threads:[~2009-03-15 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 22:42 use generic pci_assign_unassign_resources Mark Takatz
2009-03-15 23:56 ` Benjamin Herrenschmidt [this message]
2009-03-16 14:40 ` Mark Takatz
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=1237161414.25062.105.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=takatz@pericle.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).