From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>
Cc: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/xe/guc: Fix missing init value and add register order check
Date: Tue, 05 Nov 2024 14:04:32 -0800 [thread overview]
Message-ID: <85r07pxrpr.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <10b081e9-1cf6-44d9-9ee2-3ce47e099273@intel.com>
On Tue, 05 Nov 2024 12:54:49 -0800, Dong, Zhanjun wrote:
> >> +
Hi Zhanjun,
> >> + case REG_64BIT_HI_DW: {
> > alan: nit: now that you have moved to a switch statement, is this { really required?
> Few concerns:
> 1. Have {} here will make it works on most compilers and ANSIC settings.
> 2. Local variable "u64 value_qw" will be limited within this case
> statement, I don't want it to be referenced on other case statement.
Do you have a compiler where it doesn't compile? Looks like you can declare
the variable following case without the brace, compiles at least with gcc.
Also, if you need the brace, the 'break' at the end should be inside the
brace. This is used in a few places in xe, you can see how it's done :)
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2024-11-05 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 18:24 [PATCH v2] drm/xe/guc: Fix missing init value and add register order check Zhanjun Dong
2024-11-04 19:31 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-04 19:32 ` ✓ CI.checkpatch: " Patchwork
2024-11-04 19:33 ` ✓ CI.KUnit: " Patchwork
2024-11-04 19:45 ` ✓ CI.Build: " Patchwork
2024-11-04 19:47 ` ✓ CI.Hooks: " Patchwork
2024-11-04 19:48 ` ✓ CI.checksparse: " Patchwork
2024-11-04 20:24 ` ✓ CI.BAT: " Patchwork
2024-11-05 12:49 ` ✗ CI.FULL: failure " Patchwork
2024-11-05 15:20 ` Dong, Zhanjun
2024-11-05 19:09 ` [PATCH v2] " Teres Alexis, Alan Previn
2024-11-05 20:54 ` Dong, Zhanjun
2024-11-05 22:04 ` Dixit, Ashutosh [this message]
2024-11-05 23:14 ` Dong, Zhanjun
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=85r07pxrpr.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=zhanjun.dong@intel.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: 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