From: Matthew Brost <matthew.brost@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/7] drm/xe: Cleanup OPEN_BRACE style issues
Date: Fri, 14 Jul 2023 14:10:33 +0000 [thread overview]
Message-ID: <ZLFXWdDsM6vpPg8D@DUT025-TGLU> (raw)
In-Reply-To: <20230713150611.7-3-francois.dugast@intel.com>
On Thu, Jul 13, 2023 at 03:06:06PM +0000, Francois Dugast wrote:
> Remove almost all existing style issues of type OPEN_BRACE reported
> by checkpatch.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/display/ext/intel_device_info.c | 11 ++++++++---
> drivers/gpu/drm/xe/xe_gt_mcr.c | 3 ++-
> 2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/ext/intel_device_info.c b/drivers/gpu/drm/xe/display/ext/intel_device_info.c
> index 29f3909e018a..9e9ccdef81f1 100644
> --- a/drivers/gpu/drm/xe/display/ext/intel_device_info.c
> +++ b/drivers/gpu/drm/xe/display/ext/intel_device_info.c
> @@ -49,9 +49,14 @@ void intel_dvo_init(struct drm_i915_private *i915) {}
> int intel_tv_init(struct drm_i915_private *i915) { return 0; }
> int assert_dsi_pll_enabled(struct drm_i915_private *i915) { return 0; }
> bool intel_sdvo_init(struct drm_i915_private *dev_priv,
> - i915_reg_t sdvo_reg, enum port port) { return false; }
> + i915_reg_t sdvo_reg, enum port port)
> +
> +{
> + return false;
> +}
> void g4x_hdmi_init(struct drm_i915_private *dev_priv,
> - i915_reg_t hdmi_reg, enum port port) {}
> + i915_reg_t hdmi_reg, enum port port)
> +{}
> int g4x_hdmi_connector_atomic_check(struct drm_connector *connector,
> - struct drm_atomic_state *state)
> + struct drm_atomic_state *state)
> { return -ENODEV; }
> diff --git a/drivers/gpu/drm/xe/xe_gt_mcr.c b/drivers/gpu/drm/xe/xe_gt_mcr.c
> index 3db550c85e32..ff4075387564 100644
> --- a/drivers/gpu/drm/xe/xe_gt_mcr.c
> +++ b/drivers/gpu/drm/xe/xe_gt_mcr.c
> @@ -429,7 +429,8 @@ static void mcr_lock(struct xe_gt *gt)
> drm_WARN_ON_ONCE(&xe->drm, ret == -ETIMEDOUT);
> }
>
> -static void mcr_unlock(struct xe_gt *gt) {
> +static void mcr_unlock(struct xe_gt *gt)
> +{
> /* Release hardware semaphore */
> if (GRAPHICS_VERx100(gt_to_xe(gt)) >= 1270)
> xe_mmio_write32(gt, STEER_SEMAPHORE, 0x1);
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-14 14:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 15:06 [Intel-xe] [PATCH 0/7] drm/xe: Code cleanup Francois Dugast
2023-07-13 15:06 ` [Intel-xe] [PATCH 1/7] drm/xe: Cleanup SPACING style issues Francois Dugast
2023-07-14 14:50 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 2/7] drm/xe: Cleanup OPEN_BRACE " Francois Dugast
2023-07-14 14:10 ` Matthew Brost [this message]
2023-08-08 10:42 ` Jani Nikula
2023-07-13 15:06 ` [Intel-xe] [PATCH 3/7] drm/xe: Cleanup POINTER_LOCATION " Francois Dugast
2023-07-14 14:11 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 4/7] drm/xe: Cleanup CODE_INDENT " Francois Dugast
2023-07-14 14:13 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 5/7] drm/xe: Cleanup TRAILING_WHITESPACE " Francois Dugast
2023-07-14 14:22 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 6/7] drm/xe: Cleanup COMPLEX_MACRO " Francois Dugast
2023-07-14 14:24 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 7/7] drm/xe: Fix typos Francois Dugast
2023-07-14 14:23 ` Matthew Brost
2023-07-13 18:37 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Code cleanup Patchwork
2023-07-13 18:37 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-13 18:38 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-13 18:42 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-13 18:43 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-13 18:44 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-13 20:33 ` [Intel-xe] [PATCH 0/7] " Rodrigo Vivi
2023-07-17 3:47 ` Lucas De Marchi
2023-08-08 10:47 ` Jani Nikula
2023-08-08 14:37 ` Lucas De Marchi
2023-08-08 15:05 ` Jani Nikula
2023-08-08 23:39 ` Lucas De Marchi
2023-08-09 15:30 ` Jani Nikula
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=ZLFXWdDsM6vpPg8D@DUT025-TGLU \
--to=matthew.brost@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox