From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/xe: Prefer BIT/GENMASK macros over shifts
Date: Tue, 23 Jan 2024 21:19:02 +0200 [thread overview]
Message-ID: <87y1cfluxl.fsf@intel.com> (raw)
In-Reply-To: <20240123190201.1599333-1-matthew.brost@intel.com>
On Tue, 23 Jan 2024, Matthew Brost <matthew.brost@intel.com> wrote:
> Using BIT/GENMASK macros is a better convention than using manual shift
> and will also fix build errors [1].
Somehow, that description doesn't match the patch!
>
> [1] http://kisskb.ellerman.id.au/kisskb/buildresult/15112475/log/
>
> Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_ct.c | 2 +-
> drivers/gpu/drm/xe/xe_guc_relay.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index ee5d99456aeb..fc5cc2b2bcc5 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -866,7 +866,7 @@ static int parse_g2h_response(struct xe_guc_ct *ct, u32 *msg, u32 len)
> */
> if (fence & CT_SEQNO_UNTRACKED) {
> if (type == GUC_HXG_TYPE_RESPONSE_FAILURE)
> - xe_gt_err(gt, "FAST_REQ H2G fence 0x%x failed! e=0x%x, h=%u\n",
> + xe_gt_err(gt, "FAST_REQ H2G fence 0x%x failed! e=0x%lx, h=%lu\n",
> fence,
> FIELD_GET(GUC_HXG_FAILURE_MSG_0_ERROR, hxg[0]),
> FIELD_GET(GUC_HXG_FAILURE_MSG_0_HINT, hxg[0]));
> diff --git a/drivers/gpu/drm/xe/xe_guc_relay.c b/drivers/gpu/drm/xe/xe_guc_relay.c
> index c0a2d8d5d3b3..2d1f19270d9a 100644
> --- a/drivers/gpu/drm/xe/xe_guc_relay.c
> +++ b/drivers/gpu/drm/xe/xe_guc_relay.c
> @@ -300,7 +300,7 @@ static int relay_send_transaction(struct xe_guc_relay *relay, struct relay_trans
> ret = -EPROTO;
> }
> if (unlikely(ret < 0)) {
> - relay_notice(relay, "Failed to send %s.%x to GuC (%pe) %*ph ...\n",
> + relay_notice(relay, "Failed to send %s.%lx to GuC (%pe) %*ph ...\n",
> guc_hxg_type_to_string(FIELD_GET(GUC_HXG_MSG_0_TYPE, buf[0])),
> FIELD_GET(GUC_HXG_REQUEST_MSG_0_ACTION, buf[0]),
> ERR_PTR(ret), (int)sizeof(u32) * txn->offset, buf);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-23 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 19:02 [PATCH] drm/xe: Prefer BIT/GENMASK macros over shifts Matthew Brost
2024-01-23 19:19 ` Jani Nikula [this message]
2024-01-23 21:04 ` Matthew Brost
2024-01-23 19:57 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-23 19:57 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-23 19:58 ` ✓ CI.KUnit: success " Patchwork
2024-01-23 20:01 ` ✗ CI.Build: failure " Patchwork
2024-01-23 20:14 ` [PATCH] " Michal Wajdeczko
2024-01-23 21:08 ` Matthew Brost
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=87y1cfluxl.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@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.