From: Kevin Tang <kevin3.tang@gmail.com> To: maarten.lankhorst@linux.intel.com, mripard@kernel.org, airlied@linux.ie, daniel@ffwll.ch, mark.rutland@arm.com, javierm@redhat.com, tzimmermann@suse.de, lukas.bulwahn@gmail.com Cc: zou_wei@huawei.com, kevin3.tang@gmail.com, pony1.wu@gmail.com, orsonzhai@gmail.com, dan.carpenter@oracle.com, zhang.lyra@gmail.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org Subject: [PATCH v2 0/3] sprd drm cover letter Date: Mon, 17 Jan 2022 16:38:17 +0800 [thread overview] Message-ID: <20220117083820.6893-1-kevin3.tang@gmail.com> (raw) v1: remove the selected DRM_KMS_CMA_HELPER in kconfig drm-sprd-fix-potential-NULL-dereference v2: fix commit comments long lines issue and drop "On linux-next" comments Split checking platform_get_resource() return value to a separate patch Use dev_warn() instead of removing the warning log Kevin Tang (3): drm/sprd: remove the selected DRM_KMS_CMA_HELPER in kconfig drm/sprd: fix potential NULL dereference drm/sprd: check the platform_get_resource() return value drivers/gpu/drm/sprd/Kconfig | 1 - drivers/gpu/drm/sprd/sprd_dpu.c | 5 +++++ drivers/gpu/drm/sprd/sprd_drm.c | 2 +- drivers/gpu/drm/sprd/sprd_dsi.c | 5 +++++ 4 files changed, 11 insertions(+), 2 deletions(-) -- 2.29.0
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Tang <kevin3.tang@gmail.com> To: maarten.lankhorst@linux.intel.com, mripard@kernel.org, airlied@linux.ie, daniel@ffwll.ch, mark.rutland@arm.com, javierm@redhat.com, tzimmermann@suse.de, lukas.bulwahn@gmail.com Cc: devicetree@vger.kernel.org, kevin3.tang@gmail.com, zhang.lyra@gmail.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, orsonzhai@gmail.com, zou_wei@huawei.com, pony1.wu@gmail.com, dan.carpenter@oracle.com Subject: [PATCH v2 0/3] sprd drm cover letter Date: Mon, 17 Jan 2022 16:38:17 +0800 [thread overview] Message-ID: <20220117083820.6893-1-kevin3.tang@gmail.com> (raw) v1: remove the selected DRM_KMS_CMA_HELPER in kconfig drm-sprd-fix-potential-NULL-dereference v2: fix commit comments long lines issue and drop "On linux-next" comments Split checking platform_get_resource() return value to a separate patch Use dev_warn() instead of removing the warning log Kevin Tang (3): drm/sprd: remove the selected DRM_KMS_CMA_HELPER in kconfig drm/sprd: fix potential NULL dereference drm/sprd: check the platform_get_resource() return value drivers/gpu/drm/sprd/Kconfig | 1 - drivers/gpu/drm/sprd/sprd_dpu.c | 5 +++++ drivers/gpu/drm/sprd/sprd_drm.c | 2 +- drivers/gpu/drm/sprd/sprd_dsi.c | 5 +++++ 4 files changed, 11 insertions(+), 2 deletions(-) -- 2.29.0
next reply other threads:[~2022-01-17 8:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 8:38 Kevin Tang [this message] 2022-01-17 8:38 ` [PATCH v2 0/3] sprd drm cover letter Kevin Tang 2022-01-17 8:38 ` [PATCH v2 1/3] drm/sprd: remove the selected DRM_KMS_CMA_HELPER in kconfig Kevin Tang 2022-01-17 8:38 ` Kevin Tang
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=20220117083820.6893-1-kevin3.tang@gmail.com \ --to=kevin3.tang@gmail.com \ --cc=airlied@linux.ie \ --cc=dan.carpenter@oracle.com \ --cc=daniel@ffwll.ch \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=javierm@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lukas.bulwahn@gmail.com \ --cc=maarten.lankhorst@linux.intel.com \ --cc=mark.rutland@arm.com \ --cc=mripard@kernel.org \ --cc=orsonzhai@gmail.com \ --cc=pony1.wu@gmail.com \ --cc=tzimmermann@suse.de \ --cc=zhang.lyra@gmail.com \ --cc=zou_wei@huawei.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.