From: Greg KH <gregkh@linuxfoundation.org>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
juan.hao@nxp.com, dri-devel@lists.freedesktop.org,
stable@vger.kernel.org
Subject: Re: [PATCH] dma-buf: keep the signaling time of merged fences
Date: Wed, 21 Jun 2023 14:35:46 +0200 [thread overview]
Message-ID: <2023062104-goggles-filter-b939@gregkh> (raw)
In-Reply-To: <44be4e13-a157-35ec-6ff7-e3a0fce057e4@amd.com>
On Wed, Jun 21, 2023 at 02:05:07PM +0200, Christian König wrote:
> Am 21.06.23 um 13:02 schrieb Greg KH:
> > 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?
>
> Sorry Greg, totally unintentionally send this CC to the stable list because
> git wasn't correctly configured.
It's fine to cc: the stable list, we WANT to see patches that are being
sent out like this before they hit the maintainers tree as you get more
review of them.
So no need to change your git configuration, this is fine.
> The patch is still under review.
Agreed, which is why it should be fixed :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-21 12:35 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
2023-06-21 12:05 ` Christian König
2023-06-21 12:35 ` Greg KH [this message]
-- 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=2023062104-goggles-filter-b939@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).