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

2020-10-01 Thread Daniel Vetter
On Wed, Sep 30, 2020 at 11:01 PM Rodrigo Vivi wrote: > > 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-

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

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

2020-09-29 Thread Vivi, Rodrigo
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 referenced commit: dim: fb8621d3bee8 ("drm/i915: Avoid allocating a vmap arena