Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH v4 06/11] drm/xe/configfs: Rename configfs_find_group() helper
Date: Mon, 28 Jul 2025 15:57:45 -0400	[thread overview]
Message-ID: <aIfWORHMHp1FkT_8@intel.com> (raw)
In-Reply-To: <20250727172009.587-7-michal.wajdeczko@intel.com>

On Sun, Jul 27, 2025 at 07:20:03PM +0200, Michal Wajdeczko wrote:
> This helper name shouldn't suggest that it iss a part of the core
> configfs API family. While around switch to use different helper
> to release a reference.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>

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

> ---
>  drivers/gpu/drm/xe/xe_configfs.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_configfs.c b/drivers/gpu/drm/xe/xe_configfs.c
> index edd52b8f0543..f5a780b8bb80 100644
> --- a/drivers/gpu/drm/xe/xe_configfs.c
> +++ b/drivers/gpu/drm/xe/xe_configfs.c
> @@ -305,7 +305,7 @@ static struct configfs_subsystem xe_configfs = {
>  	},
>  };
>  
> -static struct xe_config_group_device *configfs_find_group(struct pci_dev *pdev)
> +static struct xe_config_group_device *find_xe_config_group_device(struct pci_dev *pdev)
>  {
>  	guard(mutex)(&xe_configfs.su_mutex);
>  	struct config_item *item;
> @@ -328,14 +328,14 @@ static struct xe_config_group_device *configfs_find_group(struct pci_dev *pdev)
>   */
>  bool xe_configfs_get_survivability_mode(struct pci_dev *pdev)
>  {
> -	struct xe_config_group_device *dev = configfs_find_group(pdev);
> +	struct xe_config_group_device *dev = find_xe_config_group_device(pdev);
>  	bool mode;
>  
>  	if (!dev)
>  		return false;
>  
>  	mode = dev->survivability_mode;
> -	config_item_put(&dev->group.cg_item);
> +	config_group_put(&dev->group);
>  
>  	return mode;
>  }
> @@ -349,7 +349,7 @@ bool xe_configfs_get_survivability_mode(struct pci_dev *pdev)
>   */
>  void xe_configfs_clear_survivability_mode(struct pci_dev *pdev)
>  {
> -	struct xe_config_group_device *dev = configfs_find_group(pdev);
> +	struct xe_config_group_device *dev = find_xe_config_group_device(pdev);
>  
>  	if (!dev)
>  		return;
> @@ -357,7 +357,7 @@ void xe_configfs_clear_survivability_mode(struct pci_dev *pdev)
>  	scoped_guard(mutex, &xe_configfs.su_mutex)
>  		dev->survivability_mode = 0;
>  
> -	config_item_put(&dev->group.cg_item);
> +	config_group_put(&dev->group);
>  }
>  
>  /**
> @@ -371,14 +371,14 @@ void xe_configfs_clear_survivability_mode(struct pci_dev *pdev)
>   */
>  u64 xe_configfs_get_engines_allowed(struct pci_dev *pdev)
>  {
> -	struct xe_config_group_device *dev = configfs_find_group(pdev);
> +	struct xe_config_group_device *dev = find_xe_config_group_device(pdev);
>  	u64 engines_allowed;
>  
>  	if (!dev)
>  		return U64_MAX;
>  
>  	engines_allowed = dev->engines_allowed;
> -	config_item_put(&dev->group.cg_item);
> +	config_group_put(&dev->group);
>  
>  	return engines_allowed;
>  }
> -- 
> 2.47.1
> 

  reply	other threads:[~2025-07-28 19:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-27 17:19 [PATCH v4 00/11] Updates for drm/xe/configfs Michal Wajdeczko
2025-07-27 17:19 ` [PATCH v4 01/11] drm/xe: Simplify module initialization code Michal Wajdeczko
2025-07-28 19:35   ` Rodrigo Vivi
2025-07-28 19:47     ` Michal Wajdeczko
2025-07-28 20:00       ` Rodrigo Vivi
2025-07-28 23:52   ` John Harrison
2025-07-29  8:39     ` Michal Wajdeczko
2025-07-27 17:19 ` [PATCH v4 02/11] drm/xe: Print module init abort code Michal Wajdeczko
2025-07-28 19:39   ` Rodrigo Vivi
2025-07-28 19:51     ` Michal Wajdeczko
2025-07-28 19:59       ` Rodrigo Vivi
2025-07-27 17:20 ` [PATCH v4 03/11] drm/xe/configfs: Destroy xe_configfs.su_mutex on exit/error Michal Wajdeczko
2025-07-28 19:42   ` Rodrigo Vivi
2025-07-27 17:20 ` [PATCH v4 04/11] drm/xe/configfs: Use mutex from xe_configfs subsystem Michal Wajdeczko
2025-07-28 19:50   ` Rodrigo Vivi
2025-07-28 19:55     ` Michal Wajdeczko
2025-07-27 17:20 ` [PATCH v4 05/11] drm/xe/configfs: Rename struct xe_config_device Michal Wajdeczko
2025-07-28 19:54   ` Rodrigo Vivi
2025-07-27 17:20 ` [PATCH v4 06/11] drm/xe/configfs: Rename configfs_find_group() helper Michal Wajdeczko
2025-07-28 19:57   ` Rodrigo Vivi [this message]
2025-07-27 17:20 ` [PATCH v4 07/11] drm/xe/configfs: Reintroduce struct xe_config_device Michal Wajdeczko
2025-07-29  0:06   ` John Harrison
2025-07-27 17:20 ` [PATCH v4 08/11] drm/xe/configfs: Keep default device config settings together Michal Wajdeczko
2025-07-29  0:07   ` John Harrison
2025-07-27 17:20 ` [PATCH v4 09/11] drm/xe/configfs: Check if device was preconfigured Michal Wajdeczko
2025-07-29  0:11   ` John Harrison
2025-07-27 17:20 ` [PATCH v4 10/11] drm/xe/configfs: Only allow configurations for supported devices Michal Wajdeczko
2025-07-27 17:20 ` [PATCH v4 11/11] drm/xe/configfs: Allow adding configurations for future VFs Michal Wajdeczko
2025-07-27 17:28 ` ✓ CI.KUnit: success for Updates for drm/xe/configfs (rev5) Patchwork
2025-07-27 18:07 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-27 19:09 ` ✓ Xe.CI.Full: " 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=aIfWORHMHp1FkT_8@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michal.wajdeczko@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