From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] dma-buf/dma-resv: Respect num_fences when initializing the shared fence list.
Date: Wed, 25 Nov 2020 10:50:15 +0100 [thread overview]
Message-ID: <95ae2c09-4907-4f99-6669-1858ae5499aa@linux.intel.com> (raw)
In-Reply-To: <a40b62d6-3285-abe6-17b7-47b89a53d89f@linux.intel.com>
Op 24-11-2020 om 14:10 schreef Thomas Hellström:
>
> On 11/24/20 12:57 PM, Maarten Lankhorst wrote:
>> We hardcode the maximum number of shared fences to 4, instead of
>> respecting num_fences. Use a minimum of 4, but more if num_fences
>> is higher.
>>
>> This seems to have been an oversight when first implementing the
>> api.
>>
>> Fixes: 04a5faa8cbe5 ("reservation: update api and add some helpers")
>> Cc: <stable@vger.kernel.org> # v3.17+
>> Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> ---
>> drivers/dma-buf/dma-resv.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
>
Thanks, pushed!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-11-25 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 11:57 [Intel-gfx] [PATCH] dma-buf/dma-resv: Respect num_fences when initializing the shared fence list Maarten Lankhorst
2020-11-24 13:10 ` Thomas Hellström
2020-11-25 9:50 ` Maarten Lankhorst [this message]
2020-11-24 16:22 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-11-24 16:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-24 21:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=95ae2c09-4907-4f99-6669-1858ae5499aa@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
/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