From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 6857/7074] htmldocs: drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c:251: warning: Function parameter or member 'range' not described in 'amdgpu_mn_invalidate_range_start_gfx'
Date: Fri, 7 Dec 2018 14:14:20 -0800 [thread overview]
Message-ID: <20181207141420.fd2afe4df9cc871a67adb82c@linux-foundation.org> (raw)
In-Reply-To: <201812061510.3O6pcsYS%fengguang.wu@intel.com>
On Thu, 6 Dec 2018 15:51:12 +0800 kbuild test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 15814356aac416bea48544b76b761d8687b5a1e9
> commit: c3a8616c95df8ced5d1acd838dc7dc384cb5276b [6857/7074] mm/mmu_notifier: use structure for invalidate_range_start/end callback
> reproduce: make htmldocs
Thanks, I did this:
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c~mm-mmu_notifier-use-structure-for-invalidate_range_start-end-callback-fix-fix
+++ a/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
@@ -238,9 +238,7 @@ static void amdgpu_mn_invalidate_node(st
* amdgpu_mn_invalidate_range_start_gfx - callback to notify about mm change
*
* @mn: our notifier
- * @mm: the mm this callback is about
- * @start: start of updated range
- * @end: end of updated range
+ * @range: mmu notifier context
*
* Block for operations on BOs to finish and mark pages as accessed and
* potentially dirty.
_
prev parent reply other threads:[~2018-12-07 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 7:51 kbuild test robot
2018-12-07 22:14 ` Andrew Morton [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=20181207141420.fd2afe4df9cc871a67adb82c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jglisse@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox