From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Dong, Zhanjun" <zhanjun.dong@intel.com>
Subject: Re: CI.checkpatch: warning for drm/xe: Expose number of dss per group and helpers
Date: Tue, 30 Jan 2024 16:00:05 +0000 [thread overview]
Message-ID: <2b3953d9e6ebdd306581ab643253cea9826e9702.camel@intel.com> (raw)
In-Reply-To: <170656785585.806401.15391310555698830368@5338d5abeb45>
On Mon, 2024-01-29 at 22:37 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe: Expose number of dss per group and helpers
> URL : https://patchwork.freedesktop.org/series/129283/
> State : warning
>
> == Summary ==
>
> + KERNEL=/kernel
> + git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
> Cloning into 'mt'...
> warning: redirecting to
> https://gitlab.freedesktop.org/drm/maintainer-tools.git/
> + git -C mt rev-list -n1 origin/master
> 35591fb8b4d5305b37ce31483f85ac0956eaa536
> + cd /kernel
> + git config --global --add safe.directory /kernel
> + git log -n1
> commit 9f286800a5b3e23be808e8961f282ad855819293
> Author: Zhanjun Dong <zhanjun.dong@intel.com>
> Date: Mon Jan 29 14:34:03 2024 -0800
>
> drm/xe: Expose number of dss per group and helpers
>
> Expose helper for dss per group, features like GuC register
> capture will need this info to prepare buffer required.
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> + /mt/dim checkpatch f4c0dac89bd3cd02a1afe5e7a91ed4bf8de4afc6 drm-
> intel
> 9f286800a drm/xe: Expose number of dss per group and helpers
> -:97: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'ss_' - possible
> side-effects?
> #97: FILE: drivers/gpu/drm/xe/xe_gt_mcr.h:40:
> +#define for_each_ss_steering(ss_, gt_, group_, instance_) \
> + for (ss_ = 0, xe_gt_get_ss_steering(gt_, 0, &group_,
> &instance_); \
> + ss_ < XE_MAX_DSS_FUSE_BITS; \
> + ss_++, xe_gt_get_ss_steering(gt_, ss_, &group_,
> &instance_)) \
> + for_each_if(_HAS_SS(gt_, group_, instance_))
>
> -:97: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'gt_' - possible
> side-effects?
> #97: FILE: drivers/gpu/drm/xe/xe_gt_mcr.h:40:
> +#define for_each_ss_steering(ss_, gt_, group_, instance_) \
> + for (ss_ = 0, xe_gt_get_ss_steering(gt_, 0, &group_,
> &instance_); \
> + ss_ < XE_MAX_DSS_FUSE_BITS; \
> + ss_++, xe_gt_get_ss_steering(gt_, ss_, &group_,
> &instance_)) \
> + for_each_if(_HAS_SS(gt_, group_, instance_))
>
> -:97: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'group_' - possible
> side-effects?
> #97: FILE: drivers/gpu/drm/xe/xe_gt_mcr.h:40:
> +#define for_each_ss_steering(ss_, gt_, group_, instance_) \
> + for (ss_ = 0, xe_gt_get_ss_steering(gt_, 0, &group_,
> &instance_); \
> + ss_ < XE_MAX_DSS_FUSE_BITS; \
> + ss_++, xe_gt_get_ss_steering(gt_, ss_, &group_,
> &instance_)) \
> + for_each_if(_HAS_SS(gt_, group_, instance_))
Were you planning on addressing the checkpatch concerns here?
-Stuart
>
> -:97: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'group_' may be
> better as '(group_)' to avoid precedence issues
> #97: FILE: drivers/gpu/drm/xe/xe_gt_mcr.h:40:
> +#define for_each_ss_steering(ss_, gt_, group_, instance_) \
> + for (ss_ = 0, xe_gt_get_ss_steering(gt_, 0, &group_,
> &instance_); \
> + ss_ < XE_MAX_DSS_FUSE_BITS; \
> + ss_++, xe_gt_get_ss_steering(gt_, ss_, &group_,
> &instance_)) \
> + for_each_if(_HAS_SS(gt_, group_, instance_))
>
> -:97: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'instance_' -
> possible side-effects?
> #97: FILE: drivers/gpu/drm/xe/xe_gt_mcr.h:40:
> +#define for_each_ss_steering(ss_, gt_, group_, instance_) \
> + for (ss_ = 0, xe_gt_get_ss_steering(gt_, 0, &group_,
> &instance_); \
> + ss_ < XE_MAX_DSS_FUSE_BITS; \
> + ss_++, xe_gt_get_ss_steering(gt_, ss_, &group_,
> &instance_)) \
> + for_each_if(_HAS_SS(gt_, group_, instance_))
>
> -:97: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'instance_' may be
> better as '(instance_)' to avoid precedence issues
> #97: FILE: drivers/gpu/drm/xe/xe_gt_mcr.h:40:
> +#define for_each_ss_steering(ss_, gt_, group_, instance_) \
> + for (ss_ = 0, xe_gt_get_ss_steering(gt_, 0, &group_,
> &instance_); \
> + ss_ < XE_MAX_DSS_FUSE_BITS; \
> + ss_++, xe_gt_get_ss_steering(gt_, ss_, &group_,
> &instance_)) \
> + for_each_if(_HAS_SS(gt_, group_, instance_))
>
> total: 0 errors, 0 warnings, 6 checks, 99 lines checked
>
>
next prev parent reply other threads:[~2024-01-30 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 22:34 [PATCH v3 0/1] drm/xe: Expose number of dss per group and helpers Zhanjun Dong
2024-01-29 22:34 ` [PATCH v3 1/1] " Zhanjun Dong
2024-01-30 16:10 ` Summers, Stuart
2024-01-29 22:37 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-29 22:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-30 16:00 ` Summers, Stuart [this message]
2024-01-29 22:38 ` ✓ CI.KUnit: success " Patchwork
2024-01-29 22:45 ` ✓ CI.Build: " Patchwork
2024-01-29 22:46 ` ✗ CI.Hooks: failure " Patchwork
2024-01-30 15:59 ` Summers, Stuart
2024-01-29 22:47 ` ✓ CI.checksparse: success " Patchwork
2024-01-29 23:10 ` ✓ CI.BAT: " Patchwork
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=2b3953d9e6ebdd306581ab643253cea9826e9702.camel@intel.com \
--to=stuart.summers@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