From: Mike Mason <mmlnx@us.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Linas Vepstas <linasvepstas@gmail.com>,
Breno Leitao <leitao@linux.vnet.ibm.com>
Subject: Re: [PATCH] eeh: Fixing a bug when pci structure is null
Date: Wed, 24 Feb 2010 14:13:35 -0800 [thread overview]
Message-ID: <4B85A48F.6090607@us.ibm.com> (raw)
In-Reply-To: <1266616485.23523.1026.camel@pasglop>
On 2/19/2010 1:54 PM, Benjamin Herrenschmidt wrote:
> On Fri, 2010-02-19 at 14:43 -0200, Breno Leitao wrote:
>> Hi Ben,
>>
>> I'd like to ask about this patch ? Should I re-submit ?
>>
>> Thanks,
>>
>> Breno Leitao wrote:
>>> During a EEH recover, the pci_dev structure can be null, mainly if an
>>> eeh event is detected during cpi config operation. In this case, the
>>> pci_dev will not be known (and will be null) the kernel will crash
>>> with the following message:
>
> It should be in -next, can you dbl check ?
I just confirmed the patch is in the -next tree.
Mike
>
> Cheers,
> Ben.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
prev parent reply other threads:[~2010-02-24 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1264789719-15591-1-git-send-email-leitao@linux.vnet.ibm.com>
2010-02-02 17:46 ` [PATCH] eeh: Fixing a bug when pci structure is null Breno Leitao
2010-02-02 18:05 ` Wolfram Sang
2010-02-03 15:56 ` Breno Leitao
2010-02-19 16:43 ` Breno Leitao
2010-02-19 17:05 ` Linas Vepstas
2010-02-19 21:55 ` Benjamin Herrenschmidt
2010-02-19 21:54 ` Benjamin Herrenschmidt
2010-02-24 22:13 ` Mike Mason [this message]
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=4B85A48F.6090607@us.ibm.com \
--to=mmlnx@us.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=leitao@linux.vnet.ibm.com \
--cc=linasvepstas@gmail.com \
--cc=linuxppc-dev@ozlabs.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 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.