From: Jordan Justen <jordan.l.justen@intel.com>
To: "Yang, Fei" <fei.yang@intel.com>,
Timo Aaltonen <tjaalton@ubuntu.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: RE: [Intel-gfx] [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL
Date: Mon, 24 Apr 2023 13:00:17 -0700 [thread overview]
Message-ID: <168236641763.392286.5740817225685975052@jljusten-skl> (raw)
In-Reply-To: <SN6PR11MB257475B612B2D78EC9801D189A9C9@SN6PR11MB2574.namprd11.prod.outlook.com>
On 2023-04-16 23:43:20, Yang, Fei wrote:
> > fei.yang@intel.com kirjoitti 17.4.2023 klo 9.24:
> >> 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.
> >
> > if I'm counting right, this would be version 5 of the series, yet
> > that is not shown anywhere nor the changes between series..
>
> Yes, mostly addressing minor issues, just want to keep the commit
> message clean as it's the enablement patch set for new platform.
One thing that could help is to use the --subject-prefix parameter to
git format-patch so "PATCH v5" would be in the subject of the emails.
Additionally, it's helpful to include full a version history in the
cover-letter (0/8) patch so it's clear what has changed in each
version of the patches sent out.
-Jordan
WARNING: multiple messages have this Message-ID (diff)
From: Jordan Justen <jordan.l.justen@intel.com>
To: "Yang, Fei" <fei.yang@intel.com>,
Timo Aaltonen <tjaalton@ubuntu.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL
Date: Mon, 24 Apr 2023 13:00:17 -0700 [thread overview]
Message-ID: <168236641763.392286.5740817225685975052@jljusten-skl> (raw)
In-Reply-To: <SN6PR11MB257475B612B2D78EC9801D189A9C9@SN6PR11MB2574.namprd11.prod.outlook.com>
On 2023-04-16 23:43:20, Yang, Fei wrote:
> > fei.yang@intel.com kirjoitti 17.4.2023 klo 9.24:
> >> 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.
> >
> > if I'm counting right, this would be version 5 of the series, yet
> > that is not shown anywhere nor the changes between series..
>
> Yes, mostly addressing minor issues, just want to keep the commit
> message clean as it's the enablement patch set for new platform.
One thing that could help is to use the --subject-prefix parameter to
git format-patch so "PATCH v5" would be in the subject of the emails.
Additionally, it's helpful to include full a version history in the
cover-letter (0/8) patch so it's clear what has changed in each
version of the patches sent out.
-Jordan
next prev parent reply other threads:[~2023-04-24 20:00 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 6:24 [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL fei.yang
2023-04-17 6:24 ` [Intel-gfx] " fei.yang
2023-04-17 6:24 ` [PATCH 1/8] drm/i915/mtl: Set has_llc=0 fei.yang
2023-04-17 6:24 ` [Intel-gfx] " fei.yang
2023-04-19 10:59 ` Andi Shyti
2023-04-19 12:50 ` Andrzej Hajda
2023-04-19 14:10 ` Das, Nirmoy
2023-04-17 6:24 ` [PATCH 2/8] drm/i915/mtl: Define MOCS and PAT tables for MTL fei.yang
2023-04-17 6:24 ` [Intel-gfx] " fei.yang
2023-04-19 11:01 ` Andi Shyti
2023-04-19 16:00 ` Yang, Fei
2023-04-19 16:00 ` Yang, Fei
2023-04-19 13:59 ` Andrzej Hajda
2023-04-19 16:03 ` Yang, Fei
2023-04-19 16:03 ` Yang, Fei
2023-04-19 14:36 ` Das, Nirmoy
2023-04-19 16:05 ` Yang, Fei
2023-04-19 16:05 ` Yang, Fei
2023-04-17 6:24 ` [PATCH 3/8] drm/i915/mtl: Add PTE encode function fei.yang
2023-04-17 6:24 ` [Intel-gfx] " fei.yang
2023-04-19 11:02 ` Andi Shyti
2023-04-19 12:51 ` Andrzej Hajda
2023-04-19 15:11 ` Das, Nirmoy
2023-04-19 15:11 ` [Intel-gfx] " Das, Nirmoy
2023-04-17 6:24 ` [PATCH 4/8] drm/i915/mtl: workaround coherency issue for Media fei.yang
2023-04-17 6:24 ` [Intel-gfx] " fei.yang
2023-04-19 10:59 ` Andi Shyti
2023-04-19 12:38 ` Andi Shyti
2023-04-19 15:14 ` Das, Nirmoy
2023-04-19 15:14 ` [Intel-gfx] " Das, Nirmoy
2023-04-19 15:40 ` Andrzej Hajda
2023-04-19 16:37 ` Yang, Fei
2023-04-19 16:37 ` Yang, Fei
2023-04-19 18:49 ` Yang, Fei
2023-04-19 18:49 ` Yang, Fei
2023-04-17 6:25 ` [PATCH 5/8] drm/i915/mtl: end support for set caching ioctl fei.yang
2023-04-17 6:25 ` [Intel-gfx] " fei.yang
2023-04-19 11:08 ` Andi Shyti
2023-04-19 13:05 ` Andrzej Hajda
2023-04-19 16:56 ` Yang, Fei
2023-04-19 16:56 ` Yang, Fei
2023-04-17 6:25 ` [PATCH 6/8] drm/i915: preparation for using PAT index fei.yang
2023-04-17 6:25 ` [Intel-gfx] " fei.yang
2023-04-19 11:17 ` Andi Shyti
2023-04-19 11:17 ` [Intel-gfx] " Andi Shyti
2023-04-17 6:25 ` [PATCH 7/8] drm/i915: use pat_index instead of cache_level fei.yang
2023-04-17 6:25 ` [Intel-gfx] " fei.yang
2023-04-19 12:16 ` Andi Shyti
2023-04-17 6:25 ` [PATCH 8/8] drm/i915: Allow user to set cache at BO creation fei.yang
2023-04-17 6:25 ` [Intel-gfx] " fei.yang
2023-04-19 12:23 ` Andi Shyti
2023-04-19 12:23 ` [Intel-gfx] " Andi Shyti
2023-04-17 6:32 ` [Intel-gfx] [PATCH 0/8] drm/i915/mtl: Define MOCS and PAT tables for MTL Timo Aaltonen
2023-04-17 6:43 ` Yang, Fei
2023-04-17 6:43 ` Yang, Fei
2023-04-24 20:00 ` Jordan Justen [this message]
2023-04-24 20:00 ` Jordan Justen
2023-04-17 11:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/mtl: Define MOCS and PAT tables for MTL (rev5) Patchwork
2023-04-17 11:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-17 12:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- 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-19 18:09 fei.yang
2023-04-19 20:37 ` Andi Shyti
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=168236641763.392286.5740817225685975052@jljusten-skl \
--to=jordan.l.justen@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fei.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tjaalton@ubuntu.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.