From: kernel test robot <lkp@intel.com>
To: Elliot Berman <quic_eberman@quicinc.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC v3 2/2] mm: guestmem: Convert address_space operations to guestmem library
Date: Thu, 14 Nov 2024 19:52:57 +0800 [thread overview]
Message-ID: <202411141918.hOFtcGfU-lkp@intel.com> (raw)
In-Reply-To: <20241113-guestmem-library-v3-2-71fdee85676b@quicinc.com>
Hi Elliot,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on 5cb1659f412041e4780f2e8ee49b2e03728a2ba6]
url: https://github.com/intel-lab-lkp/linux/commits/Elliot-Berman/KVM-guest_memfd-Convert-free_folio-to-release_folio/20241114-063557
base: 5cb1659f412041e4780f2e8ee49b2e03728a2ba6
patch link: https://lore.kernel.org/r/20241113-guestmem-library-v3-2-71fdee85676b%40quicinc.com
patch subject: [PATCH RFC v3 2/2] mm: guestmem: Convert address_space operations to guestmem library
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241114/202411141918.hOFtcGfU-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241114/202411141918.hOFtcGfU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411141918.hOFtcGfU-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/guestmem.c:214: warning: expecting prototype for guestmem_put_folio(). Prototype was for guestmem_punch_hole() instead
vim +214 mm/guestmem.c
203
204 /**
205 * guestmem_put_folio() - Helper to punch a hole in a guestmem mapping
206 * @mapping: The address space to punch a hole in
207 * @offset: The offset to punch a hole at
208 * @len: The length of the hole to punch
209 *
210 * Return: 0 on success, -errno on failure.
211 */
212 int guestmem_punch_hole(struct address_space *mapping, loff_t offset,
213 loff_t len)
> 214 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-14 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 22:34 [PATCH RFC v3 0/2] mm: Refactor KVM guest_memfd to introduce guestmem library Elliot Berman
2024-11-13 22:34 ` [PATCH RFC v3 1/2] KVM: guest_memfd: Convert .free_folio() to .release_folio() Elliot Berman
2024-11-15 10:58 ` David Hildenbrand
2024-11-15 10:58 ` David Hildenbrand
2024-11-15 20:13 ` Elliot Berman
2024-11-18 9:38 ` David Hildenbrand
2024-11-13 22:34 ` [PATCH RFC v3 2/2] mm: guestmem: Convert address_space operations to guestmem library Elliot Berman
2024-11-14 11:52 ` kernel test robot [this message]
2024-11-15 10:31 ` [PATCH RFC v3 0/2] mm: Refactor KVM guest_memfd to introduce " 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=202411141918.hOFtcGfU-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_eberman@quicinc.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.