From: Guenter Roeck <linux@roeck-us.net> To: Peng Hao <peng.hao2@zte.com.cn> Cc: alexander.deucher@amd.com, christian.koenig@amd.com, David1.Zhou@amd.com, airlied@linux.ie, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] amdgpu/gmc : fix compile warning Date: Thu, 4 Oct 2018 11:52:37 -0700 [thread overview] Message-ID: <20181004185237.GA20667@roeck-us.net> (raw) In-Reply-To: <1536919552-116245-1-git-send-email-peng.hao2@zte.com.cn> Hi, On Fri, Sep 14, 2018 at 06:05:52PM +0800, Peng Hao wrote: > drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c: > In function ‘gmc_v8_0_process_interrupt’: > drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c:1447:10: > warning: missing braces around initializer [-Wmissing-braces] > > Signed-off-by: Peng Hao <peng.hao2@zte.com.cn> Was there any feedback on this patch ? The problem does affect us, and we'll need a fix. > --- > drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c | 2 +- > drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c > index 9333109..55f4755 100644 > --- a/drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c > +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c > @@ -1444,7 +1444,7 @@ static int gmc_v8_0_process_interrupt(struct amdgpu_device *adev, > gmc_v8_0_set_fault_enable_default(adev, false); > > if (printk_ratelimit()) { > - struct amdgpu_task_info task_info = { 0 }; > + struct amdgpu_task_info task_info = { {0} }; > I wondered if struct amdgpu_task_info task_info = { }; would be better. Thanks, Guenter > amdgpu_vm_get_task_info(adev, entry->pasid, &task_info); > > diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c > index 72f8018..e8b78c5 100644 > --- a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c > +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c > @@ -259,7 +259,7 @@ static int gmc_v9_0_process_interrupt(struct amdgpu_device *adev, > } > > if (printk_ratelimit()) { > - struct amdgpu_task_info task_info = { 0 }; > + struct amdgpu_task_info task_info = { {0} }; > > amdgpu_vm_get_task_info(adev, entry->pasid, &task_info); >
next prev parent reply other threads:[~2018-10-04 18:52 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-14 10:05 Peng Hao 2018-10-04 18:52 ` Guenter Roeck [this message] 2018-10-05 8:14 ` Koenig, Christian 2018-10-05 8:38 ` Guenter Roeck 2018-10-08 8:00 ` Christian König 2018-10-08 13:33 ` Guenter Roeck 2018-10-08 13:47 ` Koenig, Christian 2018-10-08 14:10 ` Guenter Roeck 2018-10-08 15:57 ` Deucher, Alexander 2018-10-08 17:22 ` Koenig, Christian 2018-10-08 17:46 ` Guenter Roeck 2018-10-08 18:13 ` Koenig, Christian 2018-10-19 8:53 ` Daniel Vetter 2018-10-19 8:56 ` Daniel Vetter 2018-10-19 13:08 ` Guenter Roeck 2018-10-19 15:30 ` Alex Deucher 2018-10-08 17:41 ` Guenter Roeck 2018-10-08 18:24 ` Deucher, Alexander
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=20181004185237.GA20667@roeck-us.net \ --to=linux@roeck-us.net \ --cc=David1.Zhou@amd.com \ --cc=airlied@linux.ie \ --cc=alexander.deucher@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=christian.koenig@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=peng.hao2@zte.com.cn \ --subject='Re: [PATCH] amdgpu/gmc : fix compile warning' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).