The merge has commit 1a3b85ea as the first parent and commit 3840ed9 as the second parent, so all the commits added by the merge should be between these two commits.
git describe --contains 1a3b85e
v4.14-rc1~150
git describe --contains 3840ed9
v4.14-rc1~149^2
And the merge:
git describe --contains e63a94f
v4.14-rc1~149
If a test kernel up to commit e63a94f fixes the bug, then a test kernel up to commit 3840ed9 should as well. If it does not, then I'll have to dig much deeper.
Commit e63a94f is a child of commit 3840ed9:
commit 3840ed9548f778717aaab5eab744da798c3ea055
Author: Miodrag Dinic <email address hidden> 2017-08-29 09:53:20
Committer: Greg Kroah-Hartman <email address hidden> 2017-08-31 12:58:45
Parent: 7157d2be23da9f8860c69e2b79184a4e02701dad (tty: goldfish: Use streaming DMA for r/w operations on Ranchu platforms)
Child: e63a94f12b5fc67b2b92a89d4058e7a9021e900e (Merge tag 'tty-4.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty)
Branches: master, remotes/next/akpm, remotes/next/akpm-base, remotes/next/master, remotes/next/stable, remotes/origin/master
Follows: v4.13-rc5
Precedes: v4.14-rc1
tty: goldfish: Implement support for kernel 'earlycon' parameter
I also built a test kernel up to commit 3840ed9 again. This kernel should fix the bug since it's the last commit added by by the merge base:
commit e63a94f12b5fc67 b2b92a89d4058e7 a9021e900e 41c2310937bf2fa ed4d036603 732fdd86b321b10 bcaeb53512 17aaab5eab744da 798c3ea055 17aaab5eab744da 798c3ea055
tree 9fddf35df3289bd
parent 1a3b85ea36d38d5
parent 3840ed9548f7787
author Linus Torvalds <email address hidden> 1504632648 -0700
committer Linus Torvalds <email address hidden> 1504632648 -0700
mergetag object 3840ed9548f7787
type commit
tag tty-4.14-rc1
tagger Greg Kroah-Hartman <email address hidden> 1504542898 +0200
TTY/Serial updates for 4.14-rc1
The merge has commit 1a3b85ea as the first parent and commit 3840ed9 as the second parent, so all the commits added by the merge should be between these two commits.
git describe --contains 1a3b85e
v4.14-rc1~150
git describe --contains 3840ed9
v4.14-rc1~149^2
And the merge:
git describe --contains e63a94f
v4.14-rc1~149
If a test kernel up to commit e63a94f fixes the bug, then a test kernel up to commit 3840ed9 should as well. If it does not, then I'll have to dig much deeper.
Commit e63a94f is a child of commit 3840ed9:
commit 3840ed9548f7787 17aaab5eab744da 798c3ea055 860c69e2b79184a 4e02701dad (tty: goldfish: Use streaming DMA for r/w operations on Ranchu platforms) b2b92a89d4058e7 a9021e900e (Merge tag 'tty-4.14-rc1' of git://git. kernel. org/pub/ scm/linux/ kernel/ git/gregkh/ tty) next/akpm- base, remotes/ next/master, remotes/ next/stable, remotes/ origin/ master
Author: Miodrag Dinic <email address hidden> 2017-08-29 09:53:20
Committer: Greg Kroah-Hartman <email address hidden> 2017-08-31 12:58:45
Parent: 7157d2be23da9f8
Child: e63a94f12b5fc67
Branches: master, remotes/next/akpm, remotes/
Follows: v4.13-rc5
Precedes: v4.14-rc1
tty: goldfish: Implement support for kernel 'earlycon' parameter
Test kernels can be found at:
3840ed9: http:// kernel. ubuntu. com/~jsalisbury /lp1724911/ 3840ed9/ kernel. ubuntu. com/~jsalisbury /lp1724911/ e63a94f/
e63a94f: http://
7157d2b: http:// kernel. ubuntu. com/~jsalisbury /lp1724911/ 7157d2b/