Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: David Kershner <david.kershner@intel.com>,
	Badal Nilawar <badal.nilawar@intel.com>,
	Riana Tauro <riana.tauro@intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: john.fleck@intel.com, stuart.summers@intel.com,
	matthew.d.roper@intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v3 2/2] drm/xe/xe_hwmon.c: Add static to xe_hwmon_process_reg_read64
Date: Wed, 4 Oct 2023 12:02:02 -0400	[thread overview]
Message-ID: <ZR2MehAL7QpxTPhV@intel.com> (raw)
In-Reply-To: <20231003222145.4090918-3-david.kershner@intel.com>

On Tue, Oct 03, 2023 at 06:21:45PM -0400, David Kershner wrote:
> Add static to xe_hwmon_process_reg_read64 to avoid compile warning:
> 
>     ../drivers/gpu/drm/xe/xe_hwmon.c:126:5: error: no previous prototype
>          for ‘xe_hwmon_process_reg_read64’ [-Werror=missing-prototypes]

yeap, non-exported functions should always be static.
and exported functions like xe_hwmon_register() should have documentation.

> 
> Signed-off-by: David Kershner <david.kershner@intel.com>

Cc: Badal Nilawar <badal.nilawar@intel.com>
Cc: Riana Tauro <riana.tauro@intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>

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

> ---
>  drivers/gpu/drm/xe/xe_hwmon.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index 1deb5007e1e2..172bb85edcf1 100644
> --- a/drivers/gpu/drm/xe/xe_hwmon.c
> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> @@ -123,7 +123,7 @@ static int xe_hwmon_process_reg(struct xe_hwmon *hwmon, enum xe_hwmon_reg hwmon_
>  	}
>  }
>  
> -int xe_hwmon_process_reg_read64(struct xe_hwmon *hwmon, enum xe_hwmon_reg hwmon_reg, u64 *value)
> +static int xe_hwmon_process_reg_read64(struct xe_hwmon *hwmon, enum xe_hwmon_reg hwmon_reg, u64 *value)
>  {
>  	struct xe_reg reg;
>  
> -- 
> 2.35.1
> 

  parent reply	other threads:[~2023-10-04 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 22:21 [Intel-xe] [PATCH v3 0/2] Use DPA offset for page table entries David Kershner
2023-10-03 22:21 ` [Intel-xe] [PATCH v3 1/2] drm/xe/xe_migrate.c: " David Kershner
2023-10-03 23:12   ` Niranjana Vishwanathapura
2023-10-04 11:31     ` Ruhl, Michael J
2023-10-05  0:16       ` Niranjana Vishwanathapura
2023-10-04 13:58     ` Kershner, David
2023-10-05  0:10       ` Niranjana Vishwanathapura
2023-10-03 22:21 ` [Intel-xe] [PATCH v3 2/2] drm/xe/xe_hwmon.c: Add static to xe_hwmon_process_reg_read64 David Kershner
2023-10-03 23:01   ` Niranjana Vishwanathapura
2023-10-04 16:02   ` Rodrigo Vivi [this message]
2023-10-05 21:22   ` Andi Shyti
2023-10-03 22:54 ` [Intel-xe] ✓ CI.Patch_applied: success for Use DPA offset for page table entries Patchwork
2023-10-03 22:55 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-03 22:56 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-03 23:03 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 23:03 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 23:05 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 23:42 ` [Intel-xe] ✓ CI.BAT: " 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=ZR2MehAL7QpxTPhV@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=david.kershner@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.fleck@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=stuart.summers@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