[PATCH] dim: drm-intel: Include drm-intel-gt-next as part of unified fixes flow

2020-09-30 Thread Rodrigo Vivi
v2: With this real minimal version provided by Jani. Credits-to: Jani Nikula Signed-off-by: Rodrigo Vivi --- dim | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dim b/dim index c3a048db8956..82d9c6f4d1ea 100755 --- a/dim +++ b/dim @@ -1384,7 +1384,7 @@ function cherry_pick_b

Re: Should we accept # comment marks on fixes and parse them out?

2020-09-30 Thread Rodrigo Vivi
On Wed, Sep 30, 2020 at 12:28:21PM +0200, Daniel Vetter wrote: > On Tue, Sep 29, 2020 at 07:37:13PM +, Vivi, Rodrigo wrote: > > Apparently #x86-32 as comment is breaking dim on the fixes flow. > > > > > > $ tdim push drm-intel-next-fixes > > dim: d6ec212e4a0d ("drm/i915/gem: Avoid implicit vm

Re: Should we accept # comment marks on fixes and parse them out?

2020-09-30 Thread Daniel Vetter
On Tue, Sep 29, 2020 at 07:37:13PM +, Vivi, Rodrigo wrote: > Apparently #x86-32 as comment is breaking dim on the fixes flow. > > > $ tdim push drm-intel-next-fixes > dim: d6ec212e4a0d ("drm/i915/gem: Avoid implicit vmap for highmem on > x86-32"): Subject in fixes line doesn't match referenc

Re: [RFC] dim: drm-intel: Include drm-intel-gt-next as part of unified fixes flow

2020-09-30 Thread Jani Nikula
On Wed, 30 Sep 2020, Jani Nikula wrote: > On Tue, 29 Sep 2020, Rodrigo Vivi wrote: >> This is the minimal and more straight forward way to do it, >> although I'm sure there are better ways. > > Hardly minimal? > > I think there's probably a magic git spell to list multiple branches to > look for

Re: [RFC] dim: drm-intel: Include drm-intel-gt-next as part of unified fixes flow

2020-09-30 Thread Jani Nikula
On Tue, 29 Sep 2020, Rodrigo Vivi wrote: > This is the minimal and more straight forward way to do it, > although I'm sure there are better ways. Hardly minimal? I think there's probably a magic git spell to list multiple branches to look for when passing the parameters to git_list_fixes. Faili