From: Greg KH <gregkh@linuxfoundation.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: juan.hao@nxp.com, dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] dma-buf: keep the signaling time of merged fences
Date: Wed, 21 Jun 2023 13:02:50 +0200 [thread overview]
Message-ID: <2023062140-bartender-closable-9fa9@gregkh> (raw)
In-Reply-To: <20230621073204.28459-1-christian.koenig@amd.com>
On Wed, Jun 21, 2023 at 09:32:04AM +0200, Christian König wrote:
> Some Android CTS is testing for that.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> CC: stable@vger.kernel.org
What commit id does this fix?
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-21 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 7:32 [PATCH] dma-buf: keep the signaling time of merged fences Christian König
2023-06-21 11:02 ` Greg KH
2023-06-21 11:02 ` Greg KH [this message]
2023-06-21 12:05 ` Christian König
2023-06-21 12:35 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-06-21 7:57 Jessie Hao
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=2023062140-bartender-closable-9fa9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=juan.hao@nxp.com \
--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;
as well as URLs for NNTP newsgroup(s).