From: Joerg Roedel <jroedel@suse.de>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: I'd like to donate a MacBook Pro
Date: Wed, 3 May 2017 16:58:42 +0200 [thread overview]
Message-ID: <20170503145842.GE5077@suse.de> (raw)
In-Reply-To: <CAMMLpeSfvvH7NuHKQC0Nzbm8ucHwnnH0VNotuTUxPvb8XEwFRA@mail.gmail.com>
On Wed, May 03, 2017 at 08:35:47AM -0600, Alex Henrie wrote:
> 2017-05-03 5:58 GMT-06:00 Greg KH <gregkh@linuxfoundation.org>:
> > On Tue, May 02, 2017 at 10:55:09PM -0600, Alex Henrie wrote:
> >> Today I ran a regression test to determine which commit made the
> >> keyboard stop working entirely. The last commit that worked for me was
> >> c09e22d5370739e16463c113525df51b5980b1d5. After that, there is a long
> >> series of commits where the screen stays black, and after that, I
> >> start getting errors like the one above.
> >
> > So git bisect said that commit was a good change, what one was the "bad"
> > commit that git bisect pointed at?
>
> The commit right after that, but it's not clear whether the screen
> blanking problem was part of the same bug or just another bug that was
> introduced at about the same time.
That would be 39ab9555c24110671f8dc671311a26e5c985b592:
iommu: Add sysfs bindings for struct iommu_device
And it introduced a regression when iommu-sysfs entries are accessed.
This is fixed in a7fdb6e648fb.
Does that commit fix the screen blanking problem?
Joerg
next prev parent reply other threads:[~2017-05-03 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 6:27 I'd like to donate a MacBook Pro Alex Henrie
2017-05-01 10:06 ` Greg KH
2017-05-03 4:55 ` Alex Henrie
2017-05-03 11:58 ` Greg KH
2017-05-03 14:35 ` Alex Henrie
2017-05-03 14:58 ` Joerg Roedel [this message]
2017-05-04 2:34 ` Alex Henrie
2017-05-11 11:16 ` Mathias Nyman
2017-05-11 20:21 ` Alex Henrie
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=20170503145842.GE5077@suse.de \
--to=jroedel@suse.de \
--cc=alexhenrie24@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox