Re: [PATCH] drm/mm: use list_next_entry

From: Daniel Vetter
Date: Wed Nov 25 2015 - 10:23:22 EST


On Wed, Nov 25, 2015 at 09:23:07PM +0800, Geliang Tang wrote:
> To make the intention clearer, use list_next_entry instead of list_entry.
>
> Signed-off-by: Geliang Tang <geliangtang@xxxxxxx>

Applied to drm-misc, thanks.
-Daniel

> ---
> include/drm/drm_mm.h | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/include/drm/drm_mm.h b/include/drm/drm_mm.h
> index a58cc6c..fc65118 100644
> --- a/include/drm/drm_mm.h
> +++ b/include/drm/drm_mm.h
> @@ -148,8 +148,7 @@ static inline u64 drm_mm_hole_node_start(struct drm_mm_node *hole_node)
>
> static inline u64 __drm_mm_hole_node_end(struct drm_mm_node *hole_node)
> {
> - return list_entry(hole_node->node_list.next,
> - struct drm_mm_node, node_list)->start;
> + return list_next_entry(hole_node, node_list)->start;
> }
>
> /**
> --
> 2.5.0
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/