All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: keep struct intel_display members sorted
Date: Tue, 14 Nov 2023 11:32:39 -0500	[thread overview]
Message-ID: <ZVOhJ1wv4pGOgsde@intel.com> (raw)
In-Reply-To: <20231114155528.96935-1-jani.nikula@intel.com>

On Tue, Nov 14, 2023 at 05:55:28PM +0200, Jani Nikula wrote:
> Like the comment says,
> 
> 	/* Grouping using anonymous structs. Keep sorted. */
> 
> Stick to it.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  .../gpu/drm/i915/display/intel_display_core.h  | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
> index aa8be02c9e54..7e82b87e9cde 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_core.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_core.h
> @@ -348,15 +348,6 @@ struct intel_display {
>  		struct intel_global_obj obj;
>  	} dbuf;
>  
> -	struct {
> -		wait_queue_head_t waitqueue;
> -
> -		/* mutex to protect pmdemand programming sequence */
> -		struct mutex lock;
> -
> -		struct intel_global_obj obj;
> -	} pmdemand;
> -
>  	struct {
>  		/*
>  		 * dkl.phy_lock protects against concurrent access of the
> @@ -444,6 +435,15 @@ struct intel_display {
>  		bool false_color;
>  	} ips;
>  
> +	struct {
> +		wait_queue_head_t waitqueue;
> +
> +		/* mutex to protect pmdemand programming sequence */
> +		struct mutex lock;
> +
> +		struct intel_global_obj obj;
> +	} pmdemand;
> +
>  	struct {
>  		struct i915_power_domains domains;
>  
> -- 
> 2.39.2
> 

  reply	other threads:[~2023-11-14 16:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 15:55 [Intel-gfx] [PATCH] drm/i915/display: keep struct intel_display members sorted Jani Nikula
2023-11-14 16:32 ` Rodrigo Vivi [this message]
2023-11-17 12:58   ` Jani Nikula
2023-11-14 23:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-11-15  0:12 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-15 21:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: keep struct intel_display members sorted (rev2) Patchwork
2023-11-15 22:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-17  5:03 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=ZVOhJ1wv4pGOgsde@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 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.