From: zhong jiang <zhongjiang@huawei.com> To: robdclark@gmail.com, airlied@linux.ie Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH linux-next] gnu: fix mismatch in function argument. Date: Tue, 24 Jul 2018 19:58:18 +0800 [thread overview] Message-ID: <1532433498-42565-1-git-send-email-zhongjiang@huawei.com> (raw) Fix the sparse error. the dpu_rm_init declaration is not consistent with the implement. Signed-off-by: zhong jiang <zhongjiang@huawei.com> --- drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h index ef3f67b..ffd1841 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h @@ -105,7 +105,7 @@ struct dpu_rm_hw_iter { */ int dpu_rm_init(struct dpu_rm *rm, struct dpu_mdss_cfg *cat, - void *mmio, + void __iomem *mmio, struct drm_device *dev); /** -- 1.7.12.4
WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com> To: <robdclark@gmail.com>, <airlied@linux.ie> Cc: <linux-arm-msm@vger.kernel.org>, <dri-devel@lists.freedesktop.org>, <freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH linux-next] gnu: fix mismatch in function argument. Date: Tue, 24 Jul 2018 19:58:18 +0800 [thread overview] Message-ID: <1532433498-42565-1-git-send-email-zhongjiang@huawei.com> (raw) Fix the sparse error. the dpu_rm_init declaration is not consistent with the implement. Signed-off-by: zhong jiang <zhongjiang@huawei.com> --- drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h index ef3f67b..ffd1841 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h @@ -105,7 +105,7 @@ struct dpu_rm_hw_iter { */ int dpu_rm_init(struct dpu_rm *rm, struct dpu_mdss_cfg *cat, - void *mmio, + void __iomem *mmio, struct drm_device *dev); /** -- 1.7.12.4
next reply other threads:[~2018-07-24 11:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-24 11:58 zhong jiang [this message] 2018-07-24 11:58 ` [PATCH linux-next] gnu: fix mismatch in function argument zhong jiang -- strict thread matches above, loose matches on Subject: below -- 2018-07-24 11:51 zhong jiang
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=1532433498-42565-1-git-send-email-zhongjiang@huawei.com \ --to=zhongjiang@huawei.com \ --cc=airlied@linux.ie \ --cc=dri-devel@lists.freedesktop.org \ --cc=freedreno@lists.freedesktop.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robdclark@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.