linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot
Date: Fri, 18 Mar 2016 08:24:51 +0100	[thread overview]
Message-ID: <20160318072451.GB1388@katana> (raw)
In-Reply-To: <3731.1458269728@turing-police.cc.vt.edu>

[-- Attachment #1: Type: text/plain, Size: 159 bytes --]


> Confirming that issue is fixed in next-20160317.

Thanks for confirming...

> Now on to fix the *next* problem :)

...and good luck with that!

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-03-18  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 14:59 next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot Valdis Kletnieks
2016-03-17 20:52 ` Wolfram Sang
2016-03-18  2:55   ` Valdis.Kletnieks
2016-03-18  7:24     ` Wolfram Sang [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=20160318072451.GB1388@katana \
    --to=wsa@the-dreams.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).