Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: <John.C.Harrison@Intel.com>, <Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/uc: Rationalise delimiters in filename macros
Date: Tue, 22 Nov 2022 15:15:06 -0800	[thread overview]
Message-ID: <d0bf1a17-0da4-cd76-3c88-39639672f965@intel.com> (raw)
In-Reply-To: <20221122200915.680629-2-John.C.Harrison@Intel.com>



On 11/22/2022 12:09 PM, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> The way delimieters (underscores and dots) were added to the UC
> filenames was different for different types of delimter. Rationalise

delimiter misspelled twice. Apart from this, it's a simple cleanup, so:

Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Daniele

> them to all be done the same way - implicitly in the concatenation
> macro rather than explicitly in the file name prefix.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
>   drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> index 0c80ba51a4bdc..774c3d84a4243 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> @@ -118,35 +118,35 @@ void intel_uc_fw_change_status(struct intel_uc_fw *uc_fw,
>    */
>   #define __MAKE_UC_FW_PATH_BLANK(prefix_, name_) \
>   	"i915/" \
> -	__stringify(prefix_) name_ ".bin"
> +	__stringify(prefix_) "_" name_ ".bin"
>   
>   #define __MAKE_UC_FW_PATH_MAJOR(prefix_, name_, major_) \
>   	"i915/" \
> -	__stringify(prefix_) name_ \
> +	__stringify(prefix_) "_" name_ "_" \
>   	__stringify(major_) ".bin"
>   
>   #define __MAKE_UC_FW_PATH_MMP(prefix_, name_, major_, minor_, patch_) \
>   	"i915/" \
> -	__stringify(prefix_) name_ \
> +	__stringify(prefix_) "_" name_  "_" \
>   	__stringify(major_) "." \
>   	__stringify(minor_) "." \
>   	__stringify(patch_) ".bin"
>   
>   /* Minor for internal driver use, not part of file name */
>   #define MAKE_GUC_FW_PATH_MAJOR(prefix_, major_, minor_) \
> -	__MAKE_UC_FW_PATH_MAJOR(prefix_, "_guc_", major_)
> +	__MAKE_UC_FW_PATH_MAJOR(prefix_, "guc", major_)
>   
>   #define MAKE_GUC_FW_PATH_MMP(prefix_, major_, minor_, patch_) \
> -	__MAKE_UC_FW_PATH_MMP(prefix_, "_guc_", major_, minor_, patch_)
> +	__MAKE_UC_FW_PATH_MMP(prefix_, "guc", major_, minor_, patch_)
>   
>   #define MAKE_HUC_FW_PATH_BLANK(prefix_) \
> -	__MAKE_UC_FW_PATH_BLANK(prefix_, "_huc")
> +	__MAKE_UC_FW_PATH_BLANK(prefix_, "huc")
>   
>   #define MAKE_HUC_FW_PATH_GSC(prefix_) \
> -	__MAKE_UC_FW_PATH_BLANK(prefix_, "_huc_gsc")
> +	__MAKE_UC_FW_PATH_BLANK(prefix_, "huc_gsc")
>   
>   #define MAKE_HUC_FW_PATH_MMP(prefix_, major_, minor_, patch_) \
> -	__MAKE_UC_FW_PATH_MMP(prefix_, "_huc_", major_, minor_, patch_)
> +	__MAKE_UC_FW_PATH_MMP(prefix_, "huc", major_, minor_, patch_)
>   
>   /*
>    * All blobs need to be declared via MODULE_FIRMWARE().


  reply	other threads:[~2022-11-22 23:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 20:09 [Intel-gfx] [PATCH 0/3] More GuC firmware version improvements John.C.Harrison
2022-11-22 20:09 ` [Intel-gfx] [PATCH 1/3] drm/i915/uc: Rationalise delimiters in filename macros John.C.Harrison
2022-11-22 23:15   ` Ceraolo Spurio, Daniele [this message]
2022-11-22 20:09 ` [Intel-gfx] [PATCH 2/3] drm/i915/uc: More refactoring of UC version numbers John.C.Harrison
2022-11-22 23:17   ` Ceraolo Spurio, Daniele
2022-11-22 20:09 ` [Intel-gfx] [PATCH 3/3] drm/i915/guc: Use GuC submission API version number John.C.Harrison
2022-11-22 23:38   ` Ceraolo Spurio, Daniele
2022-11-22 21:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for More GuC firmware version improvements Patchwork
2022-11-22 21:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-11-22 22:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-23 13:30 ` [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=d0bf1a17-0da4-cd76-3c88-39639672f965@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=DRI-Devel@Lists.FreeDesktop.Org \
    --cc=Intel-GFX@Lists.FreeDesktop.Org \
    --cc=John.C.Harrison@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