On 3 July 2017 at 09:19, Greg KH gregkh@google.com wrote:
On Mon, Jul 03, 2017 at 10:17:32AM +0200, Greg KH wrote:
On Mon, Jul 03, 2017 at 09:08:08AM +0100, Milosz Wasilewski wrote:
On 23 June 2017 at 12:22, Mark Brown broonie@kernel.org wrote:
On Wed, Jun 21, 2017 at 09:48:41PM +0100, Milosz Wasilewski wrote:
On 21 June 2017 at 15:42, Mark Brown broonie@kernel.org wrote:
On Wed, Jun 21, 2017 at 12:03:01PM +0000, Linaro QA wrote:
> kernel-describe: 8853995
This looks like it's taken a step backwards?
I'll check but I think this is how it works on this tree.
Really, no. *All* kernels should end up with something based off a tag.
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git remote -v origin https://android.googlesource.com/kernel/hikey-linaro (fetch) origin https://android.googlesource.com/kernel/hikey-linaro (push) milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git branch
- android-hikey-linaro-4.4 android-hikey-linaro-4.9 master
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git describe --always 6b116e0f
and 4.9
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git branch android-hikey-linaro-4.4
- android-hikey-linaro-4.9 master
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git describe --always db724a5
Anything I'm doing wrong?
Do you not have the upstream branch that contains the git tags for the releases? You will need that.
I recently moved the KernelCI jenkins scripts into git, so here's how our build trigger makes sure to fetch Linus tree so we have the tags to create a sensible git describe. https://github.com/kernelci/kernelci-build/blob/master/jenkins/kernel-trigge...
And to be clear, the android branches do not contain the upstream stable tags for various odd build-system reasons (i.e. it wrecks havoc with them, and the last time I tried to fix it, it took me a few days, and it still wasn't working properly...)
thanks,
greg k-h _______________________________________________ Kernel-build-reports mailing list Kernel-build-reports@lists.linaro.org https://lists.linaro.org/mailman/listinfo/kernel-build-reports