From: Alistair Popple <apopple@nvidia.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ralph Campbell <rcampbell@nvidia.com>,
nouveau@lists.freedesktop.org,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, stable@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Nouveau] [PATCH v2] mm: Take a page reference when removing device exclusive entries
Date: Thu, 30 Mar 2023 14:11:29 +1100 [thread overview]
Message-ID: <875yajapzz.fsf@nvidia.com> (raw)
In-Reply-To: <ZCTykyabcaS98Jnm@infradead.org>
Christoph Hellwig <hch@infradead.org> writes:
> s/page/folio/ in the entire commit log?
I debated that but settled on leaving it as is because device exclusive
entries only deal with non-compound pages for now and didn't want to
give any other impression. Happy to change that though if people think
it would be better/clearer.
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Popple <apopple@nvidia.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Ralph Campbell <rcampbell@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
nouveau@lists.freedesktop.org,
Matthew Wilcox <willy@infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] mm: Take a page reference when removing device exclusive entries
Date: Thu, 30 Mar 2023 14:11:29 +1100 [thread overview]
Message-ID: <875yajapzz.fsf@nvidia.com> (raw)
In-Reply-To: <ZCTykyabcaS98Jnm@infradead.org>
Christoph Hellwig <hch@infradead.org> writes:
> s/page/folio/ in the entire commit log?
I debated that but settled on leaving it as is because device exclusive
entries only deal with non-compound pages for now and didn't want to
give any other impression. Happy to change that though if people think
it would be better/clearer.
next prev parent reply other threads:[~2023-03-30 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 1:25 [Nouveau] [PATCH v2] mm: Take a page reference when removing device exclusive entries Alistair Popple
2023-03-30 1:25 ` Alistair Popple
2023-03-30 1:44 ` [Nouveau] " John Hubbard
2023-03-30 1:44 ` John Hubbard
2023-03-30 2:23 ` [Nouveau] " Christoph Hellwig
2023-03-30 2:23 ` Christoph Hellwig
2023-03-30 3:11 ` Alistair Popple [this message]
2023-03-30 3:11 ` Alistair Popple
2023-04-03 12:02 ` [Nouveau] " David Hildenbrand
2023-04-03 12:02 ` David Hildenbrand
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=875yajapzz.fsf@nvidia.com \
--to=apopple@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rcampbell@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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.