Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: fei.yang@intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL
Date: Wed, 19 Apr 2023 22:37:32 +0200	[thread overview]
Message-ID: <ZEBRDLC4RidF6Xga@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230419180942.2494156-1-fei.yang@intel.com>

Hi Fei,

On Wed, Apr 19, 2023 at 11:09:34AM -0700, fei.yang@intel.com wrote:
> From: Fei Yang <fei.yang@intel.com>
> 
> The series includes patches needed to enable MTL.
> Also add new extension for GEM_CREATE uAPI to let
> user space set cache policy for buffer objects.
> 
> v2: addressing review comments and checkpatch warnings
> 
> Fei Yang (7):
>   drm/i915/mtl: Set has_llc=0
>   drm/i915/mtl: Add PTE encode function
>   drm/i915/mtl: workaround coherency issue for Media
>   drm/i915/mtl: end support for set caching ioctl
>   drm/i915: preparation for using PAT index
>   drm/i915: use pat_index instead of cache_level
>   drm/i915: Allow user to set cache at BO creation
> 
> Madhumitha Tolakanahalli Pradeep (1):
>   drm/i915/mtl: Define MOCS and PAT tables for MTL

next time could you please add all the r-b's you got, as it's
hard to track them down?

And, could you please version your patches with format patch:

   git format-patch -v X

and also add a changelog. The changelog might be a bit annoying
but it's very useful to understand what has changed.

As a reviewer, in order to check the different versions I had to
check the date sent.

Thanks,
Andi

  parent reply	other threads:[~2023-04-19 20:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 18:09 [Intel-gfx] [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 1/8] drm/i915/mtl: Set has_llc=0 fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 2/8] drm/i915/mtl: Define MOCS and PAT tables for MTL fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 3/8] drm/i915/mtl: Add PTE encode function fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 4/8] drm/i915/mtl: workaround coherency issue for Media fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 5/8] drm/i915/mtl: end support for set caching ioctl fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 6/8] drm/i915: preparation for using PAT index fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 7/8] drm/i915: use pat_index instead of cache_level fei.yang
2023-04-19 18:09 ` [Intel-gfx] [PATCH 8/8] drm/i915: Allow user to set cache at BO creation fei.yang
2023-04-19 18:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Define MOCS and PAT tables for MTL (rev6) Patchwork
2023-04-19 18:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-19 20:37 ` Andi Shyti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-19 23:00 [Intel-gfx] [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL fei.yang
2023-04-20 11:30 ` Andi Shyti
2023-04-19 21:12 fei.yang
2023-04-17  6:24 fei.yang
2023-04-17  6:32 ` Timo Aaltonen
2023-04-17  6:43   ` Yang, Fei
2023-04-24 20:00     ` Jordan Justen
2023-04-07  7:12 fei.yang

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=ZEBRDLC4RidF6Xga@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fei.yang@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