All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Tero Roponen <tero.roponen@gmail.com>
Cc: Martin Fuzzey <mfuzzey@parkeon.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] base/platform: Fix platform drivers with no probe callback (ex alarmtimer)
Date: Tue, 5 Jan 2016 14:02:21 +0100	[thread overview]
Message-ID: <20160105130221.GC11029@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.20.1601051157580.2148@terrop.lan>

On Tue, Jan 05, 2016 at 12:02:23PM +0200, Tero Roponen wrote:
> 
> On Tue, 5 Jan 2016, Uwe Kleine-König wrote:
> 
> > Hello,
> > 
> > I think this is the same problem that another Martin found and fixed in
> > 
> > http://mid.gmane.org/1449132704-9952-1-git-send-email-martin.wilck@ts.fujitsu.com
> > 
> > I didn't check, but thought Greg already picked that up?!
> 
> I can confirm that applying the patch in that link to 4.4-rc8 fixes the
> following problem I've seen since 4.4-rc5:
> 
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000e20
> IP: [<ffffffffa017835e>] asus_sysfs_is_visible+0xe/0x1d0 [asus_laptop]

This is a separate bug however that is worth fixing, too. I guess this
is similar to the tpm problem my broken patch made obvious.

Best regards
Uwe


-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2016-01-05 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 18:17 [PATCH] base/platform: Fix platform drivers with no probe callback (ex alarmtimer) Martin Fuzzey
2016-01-05  8:43 ` Uwe Kleine-König
2016-01-05 10:02   ` Tero Roponen
2016-01-05 13:02     ` Uwe Kleine-König [this message]
2016-01-05 11:14   ` Martin Fuzzey

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=20160105130221.GC11029@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfuzzey@parkeon.com \
    --cc=tero.roponen@gmail.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 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.