From: Daniel Vetter <daniel@ffwll.ch>
To: Sasha Levin <sashal@kernel.org>
Cc: "Gustavo Padovan" <gustavo@padovan.org>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
"Sean Paul" <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free
Date: Wed, 14 Aug 2019 19:24:15 +0200 [thread overview]
Message-ID: <20190814172415.GN7444@phenom.ffwll.local> (raw)
In-Reply-To: <20190812190548.450CF20684@mail.kernel.org>
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.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-14 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson
2019-08-12 16:13 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-08-12 16:46 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-12 17:04 ` [PATCH] " Koenig, Christian
2019-08-12 19:05 ` Sasha Levin
2019-08-12 23:52 ` ✗ Fi.CI.IGT: failure for " Patchwork
[not found] ` <20190812190548.450CF20684@mail.kernel.org>
2019-08-14 17:24 ` Daniel Vetter [this message]
2019-08-15 1:46 ` [PATCH] " Sasha Levin
2019-08-15 6:47 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190814172415.GN7444@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sashal@kernel.org \
--cc=seanpaul@chromium.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox