From: Michael Ellerman <mpe@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
bobby.prani@gmail.com
Subject: Re: powerpc/book3s_32: Fix build error with checkpoint restart
Date: Sun, 31 Jan 2016 19:37:38 +1100 (AEDT) [thread overview]
Message-ID: <20160131083738.AA047140C40@ozlabs.org> (raw)
In-Reply-To: <1454086969-21074-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Fri, 2016-29-01 at 17:02:49 UTC, "Aneesh Kumar K.V" wrote:
> In file included from mm/vmscan.c:54:0:
> include/linux/swapops.h: In function ‘pte_to_swp_entry’:
> include/linux/swapops.h:69:2: error: implicit declaration of function ‘pte_swp_soft_dirty’ [-Werror=implicit-function-declaration]
> if (pte_swp_soft_dirty(pte))
> ^
> include/linux/swapops.h:70:3: error: implicit declaration of function ‘pte_swp_clear_soft_dirty’ [-Werror=implicit-function-declaration]
> pte = pte_swp_clear_soft_dirty(pte);
>
> We support soft dirty tracking only with book3s 64 for now.
> So change the Kconfig dependency accordingly. Also CHECKPOINT_RESTORE
> feature is not really dependent on SOFT_DIRTY. We track the dependency
> between MEM_SOFT_DIRTY and ARCH_SOFT_DIRTY through headers
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/19f97c98307115f5a6b0bbf848
cheers
prev parent reply other threads:[~2016-01-31 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 17:02 [PATCH] powerpc/book3s_32: Fix build error with checkpoint restart Aneesh Kumar K.V
2016-01-31 8:37 ` Michael Ellerman [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=20160131083738.AA047140C40@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bobby.prani@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).