From: "Christian König" <christian.koenig@amd.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/2] drm/mm: Add an iterator to optimally walk over holes suitable for an allocation
Date: Tue, 15 Feb 2022 08:37:38 +0100 [thread overview]
Message-ID: <30de1989-6fee-d94a-7d99-6a3a8c59659d@amd.com> (raw)
In-Reply-To: <20220214235625.864939-1-vivek.kasireddy@intel.com>
Am 15.02.22 um 00:56 schrieb Vivek Kasireddy:
> The first patch is a drm core patch that replaces the for loop in
> drm_mm_insert_node_in_range() with the iterator and would not
> cause any functional changes. The second patch is a i915 driver
> specific patch that also uses the iterator but solves a different
> problem.
Sounds like a good idea to me, but I somehow only see the cover letter
and none of the patches.
Please double check your mail setup, looks like you CCed me only on the
first mail and I don't see the rest on dri-devel for some reason.
Regards,
Christian.
>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> Cc: Christian König <christian.koenig@amd.com>
>
> Vivek Kasireddy (2):
> drm/mm: Add an iterator to optimally walk over holes for an allocation
> (v3)
> drm/i915/gem: Don't try to map and fence large scanout buffers (v7)
>
> drivers/gpu/drm/drm_mm.c | 32 ++++-----
> drivers/gpu/drm/i915/i915_gem.c | 120 +++++++++++++++++++++++---------
> include/drm/drm_mm.h | 36 ++++++++++
> 3 files changed, 137 insertions(+), 51 deletions(-)
>
next prev parent reply other threads:[~2022-02-15 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 23:56 [Intel-gfx] [PATCH 0/2] drm/mm: Add an iterator to optimally walk over holes suitable for an allocation Vivek Kasireddy
2022-02-14 23:56 ` [Intel-gfx] [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v3) Vivek Kasireddy
2022-02-14 23:56 ` [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v7) Vivek Kasireddy
2022-02-15 7:37 ` Christian König [this message]
2022-02-15 22:23 ` [Intel-gfx] [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v3) Vivek Kasireddy
2022-02-16 10:36 ` Christian König
2022-02-21 12:42 ` Tvrtko Ursulin
2022-02-16 3:16 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/mm: Add an iterator to optimally walk over holes suitable for an allocation Patchwork
2022-02-16 3:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-16 3:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-16 8:17 ` [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=30de1989-6fee-d94a-7d99-6a3a8c59659d@amd.com \
--to=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@intel.com \
--cc=vivek.kasireddy@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