Yes that is the correct kernel. The mainline-build-one script uses the 'git describe' command to come up with the name. That command returns the closest git tag and not the one that contains it. So in the case of commit d38162e4b5c643733792f32be4ea107c831827b4:
Yes that is the correct kernel. The mainline-build-one script uses the 'git describe' command to come up with the name. That command returns the closest git tag and not the one that contains it. So in the case of commit d38162e4b5c6437 33792f32be4ea10 7c831827b4:
git describe d38162e4b5c6437 33792f32be4ea10 7c831827b4 13-gd38162e
v4.12-rc1-
However, that test kernel is actually using commits in -rc4, which you can see if the '--contains' option is given to git describe:
git describe --contains d38162e4b5c6437 33792f32be4ea10 7c831827b4 20^2~4^ 2~3
v4.12-rc4~
I can continue to build the kernels, there are about 3 left. It only takes about 15 minutes to build the kernel for me.