From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: martin.wilck@ts.fujitsu.com, gregkh@linuxfoundation.org,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
u.kleine-koenig@pengutronix.de
Subject: Re: [tpmdd-devel] [PATCH] base/platform: fix panic when probe function is NULL
Date: Mon, 30 Nov 2015 14:50:05 +0200 [thread overview]
Message-ID: <20151130125005.GC15542@intel.com> (raw)
In-Reply-To: <20151128225251.GB11188@obsidianresearch.com>
On Sat, Nov 28, 2015 at 03:52:51PM -0700, Jason Gunthorpe wrote:
> On Sat, Nov 28, 2015 at 06:40:03PM +0200, Jarkko Sakkinen wrote:
> > > I have some patches to do this that are part of my OF enablement
> > > series, but I can make something simpler that would deal with this
> > > fairly quickly if you can test.
> >
> > Does the patch set that you sent include the fix or not? I haven't yet
> > reviewed them properly.
>
> No fixing probe is another task. I can send some patches for that when
> we are done with the IRQ stuff. That is something we should fix no
> matter what..
>
> BTW, please test my IRQ series, I forgot to mention I was unable to
> test it properly here...
Got you. I need to at least test insmod/rmod (maybe couple of times in a
cycle). Do you see any other code paths that could easily break because
of your patches?
> Jason
/Jarkko
next prev parent reply other threads:[~2015-11-30 12:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 19:01 [PATCH] base/platform: fix panic when probe function is NULL martin.wilck
2015-11-26 20:30 ` [tpmdd-devel] " Jason Gunthorpe
2015-11-27 7:32 ` Wilck, Martin
2015-11-28 16:40 ` Jarkko Sakkinen
2015-11-28 16:49 ` Jarkko Sakkinen
2015-11-28 22:52 ` Jason Gunthorpe
2015-11-30 12:50 ` Jarkko Sakkinen [this message]
2015-11-27 10:11 ` Uwe Kleine-König
2015-11-30 7:42 ` Wilck, Martin
2015-11-30 11:50 ` [PATCH v2] base/platform: return success " martin.wilck
2015-12-01 20:30 ` Uwe Kleine-König
2015-12-01 10:41 ` [PATCH] base/platform: fix panic " Wilck, Martin
2015-12-01 13:24 ` Uwe Kleine-König
2015-12-01 15:19 ` Wilck, Martin
2015-12-01 17:25 ` [tpmdd-devel] " Jason Gunthorpe
2015-12-01 18:26 ` Peter Huewe
2015-12-01 18:40 ` Jason Gunthorpe
2015-12-01 18:54 ` Aw: " Peter Huewe
2015-12-01 19:03 ` Jason Gunthorpe
2015-11-28 16:34 ` Jarkko Sakkinen
2015-11-29 9:54 ` Uwe Kleine-König
2015-11-30 12:56 ` Jarkko Sakkinen
2015-11-30 13:06 ` Jarkko Sakkinen
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=20151130125005.GC15542@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.wilck@ts.fujitsu.com \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=u.kleine-koenig@pengutronix.de \
/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