From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [GIT PATCH] PCI patches for 2.6.15 - retry
Date: Mon, 9 Jan 2006 16:44:10 -0800 [thread overview]
Message-ID: <20060109164410.3304a0f6.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0601091557480.5588@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
>
>
>
> On Mon, 9 Jan 2006, Greg KH wrote:
> >
> > Here are some PCI patches against your latest git tree. They have all
> > been in the -mm tree for a while with no problems. I've pulled out all
> > of the offending patches that people objected to, or ones that crashed
> > older machines from the last series I sent you.
>
> Before I pull this, I'd like to get some confirmation that some of the
> other problems that seem to be PCI-related in the -mm tree are also
> understood, or at least known to be part of the stuff that you're _not_
> sending me..
It's really hard to keep track of all this, so it's likely that some things
will still sneak through.
- Reuben Farrelly's oops in make_class_name(). Could be libata, or scsi
or driver core.
- A few problems with ehci. For example Grant Coady went oops loading
the module. Probably USB, maybe solved now, but there are
interactions...
- gregkh-pci-x86-pci-domain-support-the-meat.patch is a problem, but
wasn't in this tree.
> [ There's at least a pci_call_probe() NULL ptr dereference report by
> Martin Bligh, I think Andrew has a few others he's tracked.. ]
Yes, Martin is reporting failures on a few machines. Hopefully he's
working out whether gregkh-pci-x86-pci-domain-support-the-meat.patch was
the culprit here. If so, I'd say we're good to go. If that's _not_ the
source then we just don't know where the failure is coming from.
All very vague, sorry.
next prev parent reply other threads:[~2006-01-10 0:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:37 Greg KH
2006-01-10 0:00 ` Linus Torvalds
2006-01-10 0:44 ` Andrew Morton [this message]
2006-01-10 1:49 ` Alan Cox
2006-01-10 1:49 ` Andrew Morton
2006-01-10 10:03 ` Reuben Farrelly
2006-01-12 3:55 ` Reuben Farrelly
2006-01-12 4:29 ` Andrew Morton
2006-01-12 4:55 ` Reuben Farrelly
2006-01-12 11:42 ` Alan Cox
2006-01-12 20:59 ` Jeff Garzik
2006-01-16 13:11 ` Reuben Farrelly
2006-01-12 20:55 ` Jeff Garzik
2006-01-13 0:16 ` Alan Cox
2006-01-10 2:28 ` 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=20060109164410.3304a0f6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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
all inboxes | Powered by JetHome®