From: Nirmoy <nirmodas@amd.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
chris@chris-wilson.co.uk, intel-gfx@lists.freedesktop.org,
nirmoy.das@amd.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/mm: remove unused rb_hole_size()
Date: Mon, 15 Jun 2020 18:36:25 +0200 [thread overview]
Message-ID: <77ebb52b-806f-8129-9237-06b0ea4515c2@amd.com> (raw)
In-Reply-To: <20200615145415.1775-1-christian.koenig@amd.com>
Reviewed-by: Nirmoy Das <nirmoy.das@amd.com>
On 6/15/20 4:54 PM, Christian König wrote:
> Just some code cleanup.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/drm_mm.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c
> index 82d2888eb7fe..425fcd3590e8 100644
> --- a/drivers/gpu/drm/drm_mm.c
> +++ b/drivers/gpu/drm/drm_mm.c
> @@ -305,11 +305,6 @@ static inline struct drm_mm_node *rb_hole_addr_to_node(struct rb_node *rb)
> return rb_entry_safe(rb, struct drm_mm_node, rb_hole_addr);
> }
>
> -static inline u64 rb_hole_size(struct rb_node *rb)
> -{
> - return rb_entry(rb, struct drm_mm_node, rb_hole_size)->hole_size;
> -}
> -
> static struct drm_mm_node *best_hole(struct drm_mm *mm, u64 size)
> {
> struct rb_node *rb = mm->holes_size.rb_root.rb_node;
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-06-15 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 14:54 [PATCH 1/3] drm/mm: remove unused rb_hole_size() Christian König
2020-06-15 14:54 ` [PATCH 2/3] drm/mm: optimize find_hole() as well Christian König
2020-06-15 16:54 ` Nirmoy
2020-06-15 14:54 ` [PATCH 3/3] drm/mm: cleanup and improve next_hole_*_addr() Christian König
2020-06-15 16:38 ` Nirmoy
2020-06-15 16:36 ` Nirmoy [this message]
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=77ebb52b-806f-8129-9237-06b0ea4515c2@amd.com \
--to=nirmodas@amd.com \
--cc=chris@chris-wilson.co.uk \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@amd.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