From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.CHECKPATCH: warning for IRQ initialization debloat and conversion to uncore
Date: Tue, 9 Apr 2019 21:20:40 +0300 [thread overview]
Message-ID: <20190409182040.GW3888@intel.com> (raw)
In-Reply-To: <9df0a9d1e92f1f43277a336102ba2d98cc534785.camel@intel.com>
On Tue, Apr 09, 2019 at 10:34:22AM -0700, Paulo Zanoni wrote:
> Em ter, 2019-04-09 às 00:44 +0000, Patchwork escreveu:
> > == Series Details ==
> >
> > Series: IRQ initialization debloat and conversion to uncore
> > URL : https://patchwork.freedesktop.org/series/59202/
> > State : warning
> >
> > == Summary ==
> >
> > $ dim checkpatch origin/drm-tip
> > 7f73d1fe31bb drm/i915: refactor the IRQ init/reset macros
> > -:114: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'which' - possible side-effects?
> > #114: FILE: drivers/gpu/drm/i915/i915_irq.c:169:
> > +#define GEN8_IRQ_RESET_NDX(type, which) \
> > + gen3_irq_reset(dev_priv, GEN8_##type##_IMR(which), \
> > + GEN8_##type##_IIR(which), GEN8_##type##_IER(which))
> >
> > -:172: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'which' - possible side-effects?
> > #172: FILE: drivers/gpu/drm/i915/i915_irq.c:236:
> > +#define GEN8_IRQ_INIT_NDX(type, which, imr_val, ier_val) \
> > + gen3_irq_init(dev_priv, GEN8_##type##_IMR(which), \
> > + GEN8_##type##_IIR(which), GEN8_##type##_IER(which), \
> > + imr_val, ier_val)
> >
> > total: 0 errors, 0 warnings, 2 checks, 135 lines checked
> > 82160241d80f drm/i915: convert the IRQ initialization functions to intel_uncore
> > 8c1c76059a41 drm/i915: fully convert the IRQ initialization macros to intel_uncore
> > -:24: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'which' - possible side-effects?
> > #24: FILE: drivers/gpu/drm/i915/i915_irq.c:169:
> > +#define GEN8_IRQ_RESET_NDX(uncore, type, which) \
> > + gen3_irq_reset((uncore), GEN8_##type##_IMR(which), \
> > GEN8_##type##_IIR(which), GEN8_##type##_IER(which))
> >
> > -:46: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'which' - possible side-effects?
> > #46: FILE: drivers/gpu/drm/i915/i915_irq.c:236:
> > +#define GEN8_IRQ_INIT_NDX(uncore, type, which, imr_val, ier_val) \
> > + gen3_irq_init((uncore), GEN8_##type##_IMR(which), \
> > GEN8_##type##_IIR(which), GEN8_##type##_IER(which), \
> > imr_val, ier_val)
>
> The whiches are not really a regression, but OK we can deal with them
> to make the robots happy.
>
> >
> > -:401: ERROR:SPACING: space prohibited before that close parenthesis ')'
> > #401: FILE: drivers/gpu/drm/i915/i915_irq.c:4228:
> > + GEN2_IRQ_RESET(uncore, );
> >
> > -:416: ERROR:SPACING: space prohibited before that ',' (ctx:WxW)
> > #416: FILE: drivers/gpu/drm/i915/i915_irq.c:4252:
> > + GEN2_IRQ_INIT(uncore, , dev_priv->irq_mask, enable_mask);
> > ^
> >
> > -:433: ERROR:SPACING: space prohibited before that close parenthesis ')'
> > #433: FILE: drivers/gpu/drm/i915/i915_irq.c:4397:
> > + GEN3_IRQ_RESET(uncore, );
> >
> > -:448: ERROR:SPACING: space prohibited before that ',' (ctx:WxW)
> > #448: FILE: drivers/gpu/drm/i915/i915_irq.c:4430:
> > + GEN3_IRQ_INIT(uncore, , dev_priv->irq_mask, enable_mask);
> > ^
> >
> > -:464: ERROR:SPACING: space prohibited before that close parenthesis ')'
> > #464: FILE: drivers/gpu/drm/i915/i915_irq.c:4508:
> > + GEN3_IRQ_RESET(uncore, );
> >
> > -:479: ERROR:SPACING: space prohibited before that ',' (ctx:WxW)
> > #479: FILE: drivers/gpu/drm/i915/i915_irq.c:4552:
> > + GEN3_IRQ_INIT(uncore, , dev_priv->irq_mask, enable_mask);
>
> For these ones I really think the spaces help. I would love to read
> some opinions. Perhaps some comment like /* paste token here */ would
> help make the code more readable and could help silence checkpatch.
> Opinions?
Or maybe rename the registers to eg. I9XX_IIR?
>
> > ^
> >
> > total: 6 errors, 0 warnings, 2 checks, 432 lines checked
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-09 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 0:37 [PATCH 0/3] IRQ initialization debloat and conversion to uncore Paulo Zanoni
2019-04-09 0:37 ` [PATCH 1/3] drm/i915: refactor the IRQ init/reset macros Paulo Zanoni
2019-04-09 18:10 ` Ville Syrjälä
2019-04-10 20:45 ` Paulo Zanoni
2019-04-09 0:37 ` [PATCH 2/3] drm/i915: convert the IRQ initialization functions to intel_uncore Paulo Zanoni
2019-04-09 0:37 ` [PATCH 3/3] drm/i915: fully convert the IRQ initialization macros " Paulo Zanoni
2019-04-09 20:21 ` Ville Syrjälä
2019-04-09 0:44 ` ✗ Fi.CI.CHECKPATCH: warning for IRQ initialization debloat and conversion to uncore Patchwork
2019-04-09 17:34 ` Paulo Zanoni
2019-04-09 18:20 ` Ville Syrjälä [this message]
2019-04-10 22:53 ` Paulo Zanoni
2019-04-11 11:04 ` Ville Syrjälä
2019-04-09 1:07 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-09 7:32 ` ✓ Fi.CI.IGT: " 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=20190409182040.GW3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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;
as well as URLs for NNTP newsgroup(s).