intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] DRM: i915: i915_perf: Fixed compiler warning
Date: Tue, 10 Aug 2021 14:02:56 +0300	[thread overview]
Message-ID: <fb010ec2-5776-58c1-93f1-400f57674402@linux.intel.com> (raw)
In-Reply-To: <20210809023342.377422-1-julius.victorian.home@gmail.com>

On 09/08/2021 05:33, Julius Victorian wrote:
> From: Julius <julius.victorian.home@gmail.com>
>
> Fixed compiler warning: "left shift of negative value"
>
> Signed-off-by: Julius Victorian <julius.victorian.home@gmail.com>

Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>


Thanks!

> ---
>   drivers/gpu/drm/i915/i915_perf.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index 9f94914958c3..7b852974241e 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -2804,7 +2804,7 @@ get_default_sseu_config(struct intel_sseu *out_sseu,
>   		 * all available subslices per slice.
>   		 */
>   		out_sseu->subslice_mask =
> -			~(~0 << (hweight8(out_sseu->subslice_mask) / 2));
> +			~(~0U << (hweight8(out_sseu->subslice_mask) / 2));
>   		out_sseu->slice_mask = 0x1;
>   	}
>   }



      parent reply	other threads:[~2021-08-10 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09  2:33 [Intel-gfx] [PATCH] DRM: i915: i915_perf: Fixed compiler warning Julius Victorian
2021-08-09 14:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-08-09 15:21 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-10 11:02 ` Lionel Landwerlin [this message]

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=fb010ec2-5776-58c1-93f1-400f57674402@linux.intel.com \
    --to=lionel.g.landwerlin@linux.intel.com \
    --cc=intel-gfx@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;
as well as URLs for NNTP newsgroup(s).