From: Christoph Hellwig <hch@infradead.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Christoph Hellwig <hch@infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Linux MM <linux-mm@kvack.org>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Thomas Hellstrom <thellstrom@vmware.com>,
Brian Paul <brianp@vmware.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Christian Koenig <christian.koenig@amd.com>,
Huang Rui <ray.huang@amd.com>
Subject: Re: [PATCH] drm/ttm: don't set page->mapping
Date: Thu, 26 Nov 2020 07:20:15 +0000 [thread overview]
Message-ID: <20201126072015.GA29730@infradead.org> (raw)
In-Reply-To: <20201125235720.GR5487@ziepe.ca>
On Wed, Nov 25, 2020 at 07:57:20PM -0400, Jason Gunthorpe wrote:
> annotate is OK, I used that for a long time..
>
> My main gripe was it didn't setup the to/cc until after the annotate
> editor closes.
I put the To/Cc into the cover letter text file.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-xfs@vger.kernel.org,
Thomas Hellstrom <thellstrom@vmware.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Christoph Hellwig <hch@infradead.org>,
Linux MM <linux-mm@kvack.org>, Huang Rui <ray.huang@amd.com>,
Brian Paul <brianp@vmware.com>,
linux-fsdevel@vger.kernel.org,
Daniel Vetter <daniel.vetter@intel.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [Intel-gfx] [PATCH] drm/ttm: don't set page->mapping
Date: Thu, 26 Nov 2020 07:20:15 +0000 [thread overview]
Message-ID: <20201126072015.GA29730@infradead.org> (raw)
In-Reply-To: <20201125235720.GR5487@ziepe.ca>
On Wed, Nov 25, 2020 at 07:57:20PM -0400, Jason Gunthorpe wrote:
> annotate is OK, I used that for a long time..
>
> My main gripe was it didn't setup the to/cc until after the annotate
> editor closes.
I put the To/Cc into the cover letter text file.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-11-26 7:21 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:25 [PATCH v4 0/3] mmu_notifier vs fs_reclaim lockdep annotations Daniel Vetter
2020-11-25 16:25 ` [Intel-gfx] " Daniel Vetter
2020-11-25 16:25 ` Daniel Vetter
2020-11-25 16:25 ` [PATCH v4 1/3] mm: Track mmu notifiers in fs_reclaim_acquire/release Daniel Vetter
2020-11-25 16:25 ` [Intel-gfx] " Daniel Vetter
2020-11-25 16:25 ` Daniel Vetter
2020-11-25 16:25 ` [PATCH v4 2/3] mm: Extract might_alloc() debug check Daniel Vetter
2020-11-25 16:25 ` [Intel-gfx] " Daniel Vetter
2020-11-25 16:25 ` Daniel Vetter
2020-11-25 16:25 ` [PATCH v4 3/3] locking/selftests: Add testcases for fs_reclaim Daniel Vetter
2020-11-25 16:25 ` [Intel-gfx] " Daniel Vetter
2020-11-25 16:25 ` Daniel Vetter
2020-11-25 16:25 ` [PATCH] drm/ttm: don't set page->mapping Daniel Vetter
2020-11-25 16:25 ` [Intel-gfx] " Daniel Vetter
2020-11-25 16:25 ` Daniel Vetter
2020-11-25 16:28 ` Daniel Vetter
2020-11-25 16:28 ` [Intel-gfx] " Daniel Vetter
2020-11-25 16:28 ` Daniel Vetter
2020-11-25 16:28 ` Daniel Vetter
2020-11-25 18:06 ` Jason Gunthorpe
2020-11-25 18:06 ` Jason Gunthorpe
2020-11-25 18:11 ` Christoph Hellwig
2020-11-25 18:11 ` [Intel-gfx] " Christoph Hellwig
2020-11-25 23:57 ` Jason Gunthorpe
2020-11-25 23:57 ` Jason Gunthorpe
2020-11-26 7:20 ` Christoph Hellwig [this message]
2020-11-26 7:20 ` [Intel-gfx] " Christoph Hellwig
2020-11-25 18:16 ` Daniel Stone
2020-11-25 18:16 ` [Intel-gfx] " Daniel Stone
2020-11-25 18:16 ` Daniel Stone
2020-11-25 18:16 ` Daniel Stone
2020-11-25 17:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/ttm: don't set page->mapping (rev2) Patchwork
2020-11-25 17:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-11-25 17:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-25 19:07 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 9:54 [PATCH 0/3] mmu_notifier fs fs_reclaim lockdep annotations Daniel Vetter
2020-11-20 9:54 ` [PATCH] drm/ttm: don't set page->mapping Daniel Vetter
2020-11-20 9:54 ` Daniel Vetter
2020-11-20 10:04 ` Christian König
2020-11-20 10:04 ` Christian König
2020-11-20 10:05 ` Daniel Vetter
2020-11-20 10:05 ` Daniel Vetter
2020-11-20 10:05 ` Daniel Vetter
2020-11-20 10:08 ` Christian König
2020-11-20 10:08 ` Christian König
2020-11-20 15:01 ` Daniel Vetter
2020-11-20 15:01 ` Daniel Vetter
2020-11-04 16:50 Daniel Vetter
2020-11-05 7:59 ` Christian König
2020-11-05 9:11 ` Daniel Vetter
2020-11-05 12:29 ` Christian König
2020-11-05 12:50 ` Daniel Vetter
2020-11-05 12:56 ` Christian König
2020-11-05 13:20 ` Daniel Vetter
2020-11-05 13:22 ` Christian König
2020-11-05 14:31 ` Daniel Vetter
2020-11-05 14:38 ` Daniel Vetter
2020-11-05 15:15 ` Christian König
2020-11-05 16:37 ` Daniel Vetter
2020-11-06 8:30 ` Christian König
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=20201126072015.GA29730@infradead.org \
--to=hch@infradead.org \
--cc=brianp@vmware.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=thellstrom@vmware.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.