On Tue, Sep 19, 2017 at 11:02:24AM -0500, Tom Gall wrote:
On Sep 19, 2017, at 10:50 AM, Mark Brown broonie@kernel.org wrote:
On Tue, Sep 19, 2017 at 04:07:04PM +0100, Milosz Wasilewski wrote:
On 19 September 2017 at 15:00, Mark Brown broonie@kernel.org wrote:
I think the problem is that you are trying to use the internal name that bits of LKFT uses as a display name for end users and that's not going to end well - you probably need at least some blanks and some splitting things up.
I'm still waiting for a proposal what and how to change. As I wrote, I have no problem changing things.
Personally for:
lkft/linux-stable-rc-4.4-oe: no regressions found in build v4.4.87-32-gb8c205d85576
I'd have something like:
stable-rc/linux-v4.4.y: no regressions found for v4.4.87-32-gb8c205d85576 on OE
Yeah I see where you’re going with that. You could further pre-pend something like:
kernel.org/stable-rc/linux-v4.4.y: no regressions found for v4.4.87-32-gb8c205d85576 on OE linaro.org/hikey-stable-rc/linux-v4.4.y: no regressions found for v4.4.87-32-gb8c205d85576 on OE AOSP/common.git/android-4.4-o: no regressions found for v4.4.87-32-gb8c205d85576 on Android
This attempts to then give more of a pointer as to where the tree is coming from.
Example 1: community tree, git name, followed by branch Example 2: linaro.org tree that blends the upstream with the hikey support for 4.4 Example 3: AOSP project etc
That's much better.
But again, I don't know what -rc you are actually testing for that first one (or really any of them.)
Your refusal to use 'make kernelversion' to drag in the -rc number seems odd to me. I can't put tags in the -rc git tree, so you can't ever work off of that, sorry.
And again, "v4.4.87-32-gb8c205d85576" only means that you are running something based on 4.4.87 + 32 patches. I generate the linux-stable-rc tree by scripts and have no idea what the git commit id is, as it gets thrown away and rewritten a lot.
Now if you said: "v4.4.88-rc1" that would make sense, as that is how everyone else refers to these trees.
If working off of the git tree is too much work, just grab the quilt series and generate your own kernel tree, or pick things up from the emails and apply those, that also works. The git tree is made to try to make it easier for you all, but please don't treat it as anyone can ever refer to a git commit id and it will be there tomorrow :)
thanks,
greg k-h