From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Date: Wed, 14 Aug 2019 21:46:41 -0400 Message-ID: <20190815014641.GB31807@sasha-vm> References: <20190812154247.20508-1-chris@chris-wilson.co.uk> <20190812190548.450CF20684@mail.kernel.org> <20190814172415.GN7444@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Return-path: Content-Disposition: inline In-Reply-To: <20190814172415.GN7444@phenom.ffwll.local> Sender: stable-owner@vger.kernel.org To: Daniel Vetter Cc: Chris Wilson , dri-devel@lists.freedesktop.org, Gustavo Padovan , intel-gfx@lists.freedesktop.org, stable@vger.kernel.org, Christian =?iso-8859-1?Q?K=F6nig?= , Sean Paul List-Id: intel-gfx@lists.freedesktop.org On Wed, Aug 14, 2019 at 07:24:15PM +0200, Daniel Vetter wrote: >Hi Sasha, > >On Mon, Aug 12, 2019 at 07:05:47PM +0000, Sasha Levin wrote: >> Hi, >> >> [This is an automated email] >> >> This commit has been processed because it contains a "Fixes:" tag, >> fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking around sync_timeline lists. >> >> The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189. >> >> v5.2.8: Build OK! >> v4.19.66: Build OK! >> v4.14.138: Build OK! >> v4.9.189: Failed to apply! Possible dependencies: >> Unable to calculate >> >> >> NOTE: The patch will not be queued to stable trees until it is upstream. >> >> How should we proceed with this patch? > >The backporting instruction has an explicit # v4.14+ in there, so failure >to apply to older kernels is expected. > >Can you perhaps teach this trick to your script perhaps? Iirc we're using >the official format even. Hey Daniel, The script knows how to read stable tags :) It tested out 4.9 because the commit also has a fixes tag pointing to d3862e44daa7 ("dma-buf/sw-sync: Fix locking around sync_timeline lists."), which was backported to 4.9. Should this not be backported to 4.9, even though the commit it fixes is there?