From: Kenneth Graunke <kenneth@whitecape.org>
To: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/gt: Move wal_get_fw_for_rmw()
Date: Thu, 22 Jun 2023 16:37:59 -0700 [thread overview]
Message-ID: <24458277.F5hiQvuxAt@mizzik> (raw)
In-Reply-To: <20230622182731.3765039-1-lucas.demarchi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Thursday, June 22, 2023 11:27:29 AM PDT Lucas De Marchi wrote:
> Move helper function to get all the forcewakes required by the wa list
> to the top, so it can be re-used by other functions.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 32 ++++++++++-----------
> 1 file changed, 16 insertions(+), 16 deletions(-)
Patches 1 and 3 are:
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Kenneth Graunke <kenneth@whitecape.org>
To: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: dri-devel@lists.freedesktop.org,
Matt Roper <matthew.d.roper@intel.com>,
stable@vger.kernel.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 1/3] drm/i915/gt: Move wal_get_fw_for_rmw()
Date: Thu, 22 Jun 2023 16:37:59 -0700 [thread overview]
Message-ID: <24458277.F5hiQvuxAt@mizzik> (raw)
In-Reply-To: <20230622182731.3765039-1-lucas.demarchi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Thursday, June 22, 2023 11:27:29 AM PDT Lucas De Marchi wrote:
> Move helper function to get all the forcewakes required by the wa list
> to the top, so it can be re-used by other functions.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 32 ++++++++++-----------
> 1 file changed, 16 insertions(+), 16 deletions(-)
Patches 1 and 3 are:
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Kenneth Graunke <kenneth@whitecape.org>
To: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915/gt: Move wal_get_fw_for_rmw()
Date: Thu, 22 Jun 2023 16:37:59 -0700 [thread overview]
Message-ID: <24458277.F5hiQvuxAt@mizzik> (raw)
In-Reply-To: <20230622182731.3765039-1-lucas.demarchi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Thursday, June 22, 2023 11:27:29 AM PDT Lucas De Marchi wrote:
> Move helper function to get all the forcewakes required by the wa list
> to the top, so it can be re-used by other functions.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 32 ++++++++++-----------
> 1 file changed, 16 insertions(+), 16 deletions(-)
Patches 1 and 3 are:
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-22 23:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 18:27 [Intel-gfx] [PATCH 1/3] drm/i915/gt: Move wal_get_fw_for_rmw() Lucas De Marchi
2023-06-22 18:27 ` Lucas De Marchi
2023-06-22 18:27 ` Lucas De Marchi
2023-06-22 18:27 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Fix context workarounds with non-masked regs Lucas De Marchi
2023-06-22 18:27 ` Lucas De Marchi
2023-06-22 18:27 ` Lucas De Marchi
2023-06-22 23:37 ` [Intel-gfx] " Kenneth Graunke
2023-06-22 23:37 ` Kenneth Graunke
2023-06-22 23:37 ` Kenneth Graunke
2023-06-23 15:49 ` [Intel-gfx] " Lucas De Marchi
2023-06-23 15:49 ` Lucas De Marchi
2023-06-23 15:49 ` Lucas De Marchi
2023-06-23 19:48 ` [Intel-gfx] " Kenneth Graunke
2023-06-23 19:48 ` Kenneth Graunke
2023-06-23 19:48 ` Kenneth Graunke
2023-06-23 21:05 ` [Intel-gfx] " Lucas De Marchi
2023-06-23 21:05 ` Lucas De Marchi
2023-06-23 21:05 ` Lucas De Marchi
2023-06-23 21:56 ` [Intel-gfx] " Matt Roper
2023-06-23 21:56 ` Matt Roper
2023-06-23 21:56 ` Matt Roper
2023-06-24 18:12 ` [Intel-gfx] " Lucas De Marchi
2023-06-24 18:12 ` Lucas De Marchi
2023-06-22 18:27 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Drop read from GEN8_L3CNTLREG in ICL workaround Lucas De Marchi
2023-06-22 18:27 ` Lucas De Marchi
2023-06-22 18:27 ` Lucas De Marchi
2023-06-22 18:29 ` kernel test robot
2023-06-22 19:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915/gt: Move wal_get_fw_for_rmw() Patchwork
2023-06-22 23:37 ` Kenneth Graunke [this message]
2023-06-22 23:37 ` [PATCH 1/3] " Kenneth Graunke
2023-06-22 23:37 ` Kenneth Graunke
2023-06-23 9:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] " 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=24458277.F5hiQvuxAt@mizzik \
--to=kenneth@whitecape.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=stable@vger.kernel.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 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.