From: Lorenzo Stoakes <lstoakes@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Hellstrom <thomas.hellstrom@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH 3/3] drm/ttm: Remove comment referencing now-removed vmf_insert_mixed_prot()
Date: Mon, 13 Mar 2023 19:38:58 +0000 [thread overview]
Message-ID: <f7c5bd29-18e5-4eed-8a13-c84d4b9c4874@lucifer.local> (raw)
In-Reply-To: <58224a49-654f-0026-4286-c6103d2057dc@amd.com>
On Mon, Mar 13, 2023 at 08:47:21AM +0100, Christian König wrote:
> Am 13.03.23 um 00:40 schrieb Lorenzo Stoakes:
> > This function no longer exists, however the prot != vma->vm_page_prot case
> > discussion has been retained and moved to vmf_insert_pfn_prot() so refer to
> > this instead.
> >
> > Signed-off-by: Lorenzo Stoakes <lstoakes@gmail.com>
>
> Reviewed-by: Christian König <christian.koenig@amd.com>
>
> Feel free to add my acked-by to the other two patches in the series and
> upstream through any branch you like.
>
> Alternatively ping me when you get rbs for the first two patches from the MM
> people and I can push this upstream through drm-misc.
>
> Thanks,
> Christian.
Thanks, much appreciated! I'd rather go through mm if possible as Andrew has
already taken for mm-unstable pending further review + that's easiest for
dealing with any mm feedback.
P.S. apologies for dropping the umlaut on your name in initial patch, I really
need to sort out my terminal which got horribly confused by non-ANSI characters :)
>
> > ---
> > drivers/gpu/drm/ttm/ttm_bo_vm.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/ttm/ttm_bo_vm.c b/drivers/gpu/drm/ttm/ttm_bo_vm.c
> > index ca7744b852f5..5df3edadb808 100644
> > --- a/drivers/gpu/drm/ttm/ttm_bo_vm.c
> > +++ b/drivers/gpu/drm/ttm/ttm_bo_vm.c
> > @@ -254,7 +254,7 @@ vm_fault_t ttm_bo_vm_fault_reserved(struct vm_fault *vmf,
> > * encryption bits. This is because the exact location of the
> > * data may not be known at mmap() time and may also change
> > * at arbitrary times while the data is mmap'ed.
> > - * See vmf_insert_mixed_prot() for a discussion.
> > + * See vmf_insert_pfn_prot() for a discussion.
> > */
> > ret = vmf_insert_pfn_prot(vma, address, pfn, prot);
>
prev parent reply other threads:[~2023-03-13 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 23:40 [PATCH 0/3] Remove drm/ttm-specific mm changes Lorenzo Stoakes
2023-03-12 23:40 ` [PATCH 1/3] mm: remove unused vmf_insert_mixed_prot() Lorenzo Stoakes
2023-03-12 23:40 ` [PATCH 2/3] mm: Remove vmf_insert_pfn_xxx_prot() for huge page-table entries Lorenzo Stoakes
2023-03-12 23:40 ` [PATCH 3/3] drm/ttm: Remove comment referencing now-removed vmf_insert_mixed_prot() Lorenzo Stoakes
2023-03-13 7:47 ` Christian König
2023-03-13 19:38 ` Lorenzo Stoakes [this message]
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=f7c5bd29-18e5-4eed-8a13-c84d4b9c4874@lucifer.local \
--to=lstoakes@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=thomas.hellstrom@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox