They are from Linus' tree, but the has is the output of 'git describe', which adds its own bits in the description. 'man git-describe' will give you the details there, but to make things easy, just grab the last 7 digits (after the 'g') so v4.6-rc2-84-g541d8f4 came from commit 541d8f4. Not sure about your particular issue, but there were a number of audio fixes today, including USB, so it might be worth testing. Thanks, Justin On Wed, Apr 6, 2016 at 10:45 AM, Bruno Wolff III <bruno@xxxxxxxx> wrote: > Are the git hashes in the change log from the expanded kernel tree > (https://git.kernel.org/cgit/linux/kernel/git/jwboyer/fedora.git/) instead > of linus' tree? > > Is there some delay in pushing data to that tree from somewhere else? > > The reason I ask is I was trying to figure out if the rc2.git1 or rc2.git2 > builds were going to have a potential fix for my usb audio problem, so it > wouldn't waste time testing kernels that wouldn't be likely to fix the > issue. I found the hash for rc2.git1 in Josh's tree but not in Linus' and I > think that doesn't include the potential fix. I am having trouble finding > the hash from rc2.git2 in either tree, but might just not be doing things > correctly. > _______________________________________________ > kernel mailing list > kernel@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/kernel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ kernel mailing list kernel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/kernel@xxxxxxxxxxxxxxxxxxxxxxx
