linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ambrož Bizjak" <abizjak.pro@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in current tree in i2c
Date: Wed, 24 Apr 2019 19:30:06 +0200	[thread overview]
Message-ID: <CAJ4FQ9AQO0=_A5ueWt41JxUcLoa8-4JSGiD3_fOHQqJwKH6gRQ@mail.gmail.com> (raw)
In-Reply-To: <20190424170418.GB4253@kroah.com>

Thanks! I just tested the patch with 4.19.36 and it works for me.

On Wed, Apr 24, 2019 at 7:04 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Wed, Apr 24, 2019 at 06:59:09PM +0200, Ambrož Bizjak wrote:
> > Hi everyone,
> >
> > This buggy i2c patch (see https://lkml.org/lkml/2018/10/27/248) has
> > just landed in stable 4.19.36 without the appropriate fix, causing
> > oops on boot on many machines. For example we're experiencing this
> > issue with the NixOS distribution
> > (https://github.com/NixOS/nixpkgs/issues/60126). I am currently trying
> > the fix (https://github.com/torvalds/linux/commit/b59dfdaef173677b0b7e10f375226c0a1114fd20)
> > and will report if fixes the crash.
>
> Good catch, that fix is needed, will go queue that up now, thanks!
>
> greg k-h

  reply	other threads:[~2019-04-24 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 16:59 Oops in current tree in i2c Ambrož Bizjak
2019-04-24 17:04 ` Greg KH
2019-04-24 17:30   ` Ambrož Bizjak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-27 16:08 Linus Torvalds
2018-10-27 16:19 ` Linus Torvalds
2018-10-27 16:20 ` Jiri Kosina
2018-10-28 10:44 ` Hans de Goede
2018-10-29  8:36   ` Benjamin Tissoires

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='CAJ4FQ9AQO0=_A5ueWt41JxUcLoa8-4JSGiD3_fOHQqJwKH6gRQ@mail.gmail.com' \
    --to=abizjak.pro@gmail.com \
    --cc=gregkh@linuxfoundation.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).