From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, linux-kernel@vger.kernel.org
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
"Jérôme Glisse" <jglisse@redhat.com>,
stable@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf: fix debugfs versus rcu and fence dumping
Date: Fri, 07 Dec 2018 13:30:49 +0000 [thread overview]
Message-ID: <20181207133050.BF151214DA@mail.kernel.org> (raw)
In-Reply-To: <20181206014103.1364-1-jglisse@redhat.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.7, v4.14.86, v4.9.143, v4.4.166, v3.18.128,
v4.19.7: Build OK!
v4.14.86: Build OK!
v4.9.143: Failed to apply! Possible dependencies:
5eb2c72c8acc ("dma-buf: fence debugging")
v4.4.166: Failed to apply! Possible dependencies:
5eb2c72c8acc ("dma-buf: fence debugging")
v3.18.128: Failed to apply! Possible dependencies:
5eb2c72c8acc ("dma-buf: fence debugging")
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-12-07 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 1:41 [PATCH] dma-buf: fix debugfs versus rcu and fence dumping jglisse
2018-12-06 8:09 ` Koenig, Christian
2018-12-06 15:21 ` Jerome Glisse
2018-12-06 16:08 ` Koenig, Christian
2018-12-06 16:19 ` Jerome Glisse
2018-12-07 13:30 ` Sasha Levin [this message]
2018-12-16 19:23 ` kbuild test robot
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=20181207133050.BF151214DA@mail.kernel.org \
--to=sashal@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.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