public inbox for [email protected]
 help / color / mirror / Atom feed
From: Andrew Morton <[email protected]>
To: kernel test robot <[email protected]>
Cc: Kefeng Wang <[email protected]>,
	[email protected],
	Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Linux Memory Management List <[email protected]>
Subject: Re: [ammarfaizi2-block:akpm/mm/mm-unstable 71/161] mm/ksm.c:2605:21: error: implicit declaration of function 'copy_mc_user_highpage'; did you mean 'copy_user_highpage'?
Date: Sat, 10 Dec 2022 13:18:26 -0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Sat, 10 Dec 2022 15:59:20 +0800 kernel test robot <[email protected]> wrote:

> Note: the ammarfaizi2-block/akpm/mm/mm-unstable HEAD 4661cf99c1e4946297434595994227e47f33c014 builds fine.
>       It only hurts bisectability.
> 
> All errors (new ones prefixed by >>):
> 
>    mm/ksm.c: In function 'ksm_might_need_to_copy':
> >> mm/ksm.c:2605:21: error: implicit declaration of function 'copy_mc_user_highpage'; did you mean 'copy_user_highpage'? [-Werror=implicit-function-declaration]
>     2605 |                 if (copy_mc_user_highpage(new_page, page, address, vma)) {
>          |                     ^~~~~~~~~~~~~~~~~~~~~

Thanks.  I have moved
mm-hwposion-support-recovery-from-ksm_might_need_to_copy.patch to the
end of the mm-stable queue so this should now be fixed.


      reply	other threads:[~2022-12-10 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  7:59 [ammarfaizi2-block:akpm/mm/mm-unstable 71/161] mm/ksm.c:2605:21: error: implicit declaration of function 'copy_mc_user_highpage'; did you mean 'copy_user_highpage'? kernel test robot
2022-12-10 21:18 ` 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=20221210131826.6512ef7e5f0cd4a9e06c414e@linux-foundation.org \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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