All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Bhanuprakash Modem" <bhanuprakash.modem@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Attach and Set vrr_enabled property (rev2)
Date: Mon, 25 Apr 2022 07:07:33 -0000	[thread overview]
Message-ID: <165087045368.32284.16657484933558148231@emeril.freedesktop.org> (raw)
In-Reply-To: <20220425064612.2993587-1-bhanuprakash.modem@intel.com>

== Series Details ==

Series: Attach and Set vrr_enabled property (rev2)
URL   : https://patchwork.freedesktop.org/series/102978/
State : warning

== Summary ==

Error: dim checkpatch failed
74f8ea70155d drm/vrr: Attach vrr_enabled property to the drm crtc
-:90: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#90: FILE: drivers/gpu/drm/drm_mode_config.c:327:
+	prop = drm_property_create_bool(dev, DRM_MODE_PROP_ATOMIC,
 			"VRR_ENABLED");

total: 0 errors, 0 warnings, 1 checks, 63 lines checked
ecc537c1ea75 drm/i915/vrr: Attach and set drm crtc vrr_enabled property



  parent reply	other threads:[~2022-04-25  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  6:46 [RFC v2 0/2] Attach and Set vrr_enabled property Bhanuprakash Modem
2022-04-25  6:46 ` [Intel-gfx] " Bhanuprakash Modem
2022-04-25  6:46 ` [RFC v2 1/2] drm/vrr: Attach vrr_enabled property to the drm crtc Bhanuprakash Modem
2022-04-25  6:46   ` [Intel-gfx] " Bhanuprakash Modem
2022-04-26 22:01   ` Navare, Manasi
2022-04-26 22:01     ` [Intel-gfx] " Navare, Manasi
2022-04-28 11:51     ` Modem, Bhanuprakash
2022-04-28 11:51       ` [Intel-gfx] " Modem, Bhanuprakash
2022-04-25  6:46 ` [RFC v2 2/2] drm/i915/vrr: Attach and set drm crtc vrr_enabled property Bhanuprakash Modem
2022-04-25  6:46   ` [Intel-gfx] " Bhanuprakash Modem
2022-04-25  7:07 ` Patchwork [this message]
2022-04-25  7:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Attach and Set vrr_enabled property (rev2) 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=165087045368.32284.16657484933558148231@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=bhanuprakash.modem@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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 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.