From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS
Date: Fri, 25 Mar 2022 11:09:21 +0100 [thread overview]
Message-ID: <e443badc-dce9-4fc7-b161-397c582039f5@linux.intel.com> (raw)
In-Reply-To: <5c33e2f1-1f1c-52c7-542a-dc8dbb9e4a06@linux.intel.com>
On 3/25/2022 11:06 AM, Das, Nirmoy wrote:
>
> On 3/25/2022 11:05 AM, Das, Nirmoy wrote:
>>
>> On 3/25/2022 11:03 AM, Das, Nirmoy wrote:
>>> Reviewed-by: Nirmoy Das <nirmoy.das@amd.com>
>> Sorry, I meant this r-b for the 2nd patch and for this one Acked-by:
>> Nirmoy Das <nirmoy.das@amd.com>
> hmm old habit, please use : Acked-by: Nirmoy Das <nirmoy.das@intel.com>
Same for patch 1 Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>. I need
to some more coffee.
next prev parent reply other threads:[~2022-03-25 10:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 17:21 [Intel-gfx] [PATCH 1/2] drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS Matthew Auld
2022-03-24 17:21 ` Matthew Auld
2022-03-24 17:21 ` [Intel-gfx] [PATCH 2/2] drm/i915/migrate: move the sanity check Matthew Auld
2022-03-24 17:21 ` Matthew Auld
2022-03-25 7:17 ` [Intel-gfx] " Thomas Hellström
2022-03-25 7:17 ` Thomas Hellström
2022-03-24 17:37 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/2] drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS Patchwork
2022-03-24 18:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-25 7:16 ` [Intel-gfx] [PATCH 1/2] " Thomas Hellström
2022-03-25 7:16 ` Thomas Hellström
2022-03-25 10:03 ` [Intel-gfx] " Das, Nirmoy
2022-03-25 10:03 ` Das, Nirmoy
2022-03-25 10:05 ` [Intel-gfx] " Das, Nirmoy
2022-03-25 10:06 ` Das, Nirmoy
2022-03-25 10:09 ` Das, Nirmoy [this message]
2022-03-25 8:53 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/2] drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS (rev2) Patchwork
2022-03-25 9:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-25 9:48 ` Matthew Auld
2022-03-25 15:34 ` Vudum, Lakshminarayana
2022-03-25 15:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-25 17:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-28 22:26 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/2] drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS (rev3) Patchwork
2022-03-28 22:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-29 1:14 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=e443badc-dce9-4fc7-b161-397c582039f5@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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.