[dim PATCH 2/7] dim: stop generating drm-intel-testing requests

2018-12-05 Thread Jani Nikula
Since the drm-intel-testing branch was introduced, we've completely shifted from testing pull requests to pre-merge patch testing and continuous testing. The drm-intel-testing branch and testing request has outlived its usefulness. Remove it. We still leave the workflow for tagging and making

[dim PATCH 1/7] dim: abstract driver date update to a subcommand

2018-12-05 Thread Jani Nikula
Abstract the driver date update to a function of its own. Make it useful for other drivers as well in case they ever need it. Signed-off-by: Jani Nikula --- dim | 24 ++-- dim.rst | 5 + 2 files changed, 23 insertions(+), 6 deletions(-) diff --git a/dim b/dim index

[dim PATCH 5/7] dim: optionally launch gitk with changelog on dim tag-branch

2018-12-05 Thread Jani Nikula
Similar to what pull-request currently does. Try to be clever about not including all unmerged changes, just the ones that haven't been tagged yet. Signed-off-by: Jani Nikula --- dim | 15 +-- dim.rst | 6 -- 2 files changed, 17 insertions(+), 4 deletions(-) diff --git

[dim PATCH 0/7] dim: tagging and pull request changes, begin dinq/din migration

2018-12-05 Thread Jani Nikula
Hi all, there's two main themes here, intertwined because it's hard to properly separate the two: * Start encouraging separate dim tag-branch and dim pull-request. It's not a requirement (yet) but start supporting it better. First, make tag-branch show changes since last tag or upstream.

[dim PATCH 3/7] dim: return early on tag-branch fail

2018-12-05 Thread Jani Nikula
Reduce indent on the happy day scenario. Update error logging while at it. Signed-off-by: Jani Nikula --- dim | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/dim b/dim index 8e782eecff70..b227f0db99dc 100755 --- a/dim +++ b/dim @@ -1892,16 +1892,16 @@

[PULL] drm-misc-fixes

2018-12-05 Thread Sean Paul
Hi Dave, drm-misc fixes for this week. Big item is the lease uevent change. It seems like there's a high degree of confidence that existing userspaces will be happy with any uevent, so it should be a non-issue. Nevertheless, it hasn't soaked for very long, so something to keep an eye on.