2017-05-03 5:58 GMT-06:00 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>:
> 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.
b0119e870837dcd15a207b4701542ebac5d19b45 is the first bad commit
commit b0119e870837dcd15a207b4701542ebac5d19b45
Author: Joerg Roedel <jroedel@xxxxxxx>
Date: Wed Feb 1 13:23:08 2017 +0100
iommu: Introduce new 'struct iommu_device'
This struct represents one hardware iommu in the iommu core
code. For now it only has the iommu-ops associated with it,
but that will be extended soon.
The register/unregister interface is also added, as well as
making use of it in the Intel and AMD IOMMU drivers.
Signed-off-by: Joerg Roedel <jroedel@xxxxxxx>
:040000 040000 cb491d4d5bd25f1b65e6c93f7e67c8594901d6e1
84a5621c5e88961cf2385566c1c28eb5375c413f M drivers
:040000 040000 5a2f0b8b829b29ef80baf6ef7cf2ba4b9bf23bf7
89ecaf2419fe0e00500c23413149f1df7bcbd693 M include
-Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
