Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: ryadav-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
To: Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
	robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
	freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org
Subject: Re: [DPU PATCH 0/3] drm/msm: Fix build warnings
Date: Tue, 03 Apr 2018 14:24:16 +0530	[thread overview]
Message-ID: <7349d8e701ac6a26d49b801edbc059ff@codeaurora.org> (raw)
In-Reply-To: <20180402201027.222813-1-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>

On 2018-04-03 01:40, Sean Paul wrote:
> Finally got around to this, I've split the worst 2 out into their own
> patches.
> 
> Sean
> 
> Sean Paul (3):
>   drm/msm: Fix uninitialized use of prefill_lines
>   drm/msm: Properly cast return with ERR_PTR
>   drm/msm: Fix dpu build warnings
Hi Sean,
Some of these issues were fixed in following patch series @ 
https://lists.freedesktop.org/archives/freedreno/2018-March/002067.html
Thanks
> 
>  drivers/gpu/drm/msm/disp/dpu1/dpu_connector.c     | 7 ++++---
>  drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c          | 2 +-
>  drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c       | 4 ++--
>  drivers/gpu/drm/msm/disp/dpu1/dpu_hw_reg_dma_v1.c | 4 ++--
>  drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c           | 3 +--
>  drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c         | 1 -
>  drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.c          | 2 +-
>  drivers/gpu/drm/msm/dpu_dbg.c                     | 2 +-
>  8 files changed, 12 insertions(+), 13 deletions(-)
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno

  parent reply	other threads:[~2018-04-03  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 20:10 [DPU PATCH 0/3] drm/msm: Fix build warnings Sean Paul
     [not found] ` <20180402201027.222813-1-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-04-02 20:10   ` [DPU PATCH 1/3] drm/msm: Fix uninitialized use of prefill_lines Sean Paul
     [not found]     ` <20180402201027.222813-2-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-04-05  4:51       ` ryadav-sgV2jX0FEOL9JmXXK+q4OQ
2018-04-02 20:10   ` [DPU PATCH 2/3] drm/msm: Properly cast return with ERR_PTR Sean Paul
2018-04-02 20:10   ` [DPU PATCH 3/3] drm/msm: Fix dpu build warnings Sean Paul
     [not found]     ` <20180402201027.222813-4-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-04-05  5:07       ` ryadav-sgV2jX0FEOL9JmXXK+q4OQ
2018-04-03  8:54   ` ryadav-sgV2jX0FEOL9JmXXK+q4OQ [this message]
     [not found]     ` <7349d8e701ac6a26d49b801edbc059ff-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-04 18:33       ` [DPU PATCH 0/3] drm/msm: Fix " Sean Paul

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=7349d8e701ac6a26d49b801edbc059ff@codeaurora.org \
    --to=ryadav-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
    --cc=abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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