From: Catalin Marinas <catalin.marinas@arm.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH, REBASED] asm-generic, mm: PTE_SPECIAL cleanup
Date: Fri, 7 Dec 2012 14:30:03 +0000 [thread overview]
Message-ID: <20121207143002.GB21233@arm.com> (raw)
In-Reply-To: <1354881321-29363-1-git-send-email-kirill.shutemov@linux.intel.com>
On Fri, Dec 07, 2012 at 11:55:21AM +0000, Kirill A. Shutemov wrote:
> diff --git a/arch/Kconfig b/arch/Kconfig
> index 6887f57..fc21a52 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -364,4 +364,10 @@ config CLONE_BACKWARDS2
> help
> Architecture has the first two arguments of clone(2) swapped.
>
> +config HAVE_PTE_SPECIAL
> + bool
> + help
> + An arch should select this symbol if it provides pte_special() and
> + mkspecial().
> +
> source "kernel/gcov/Kconfig"
...
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index ef90d61..1e2d450 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -32,7 +32,8 @@ config ARM64
> select RTC_LIB
> select SPARSE_IRQ
> select SYSCTL_EXCEPTION_TRACE
> - select CLONE_BACKWARDS
> + select CHAVE_SPARSE_IRQLONE_BACKWARDS
> + select HAVE_SPARSE_IRQ
> help
> ARM 64-bit (AArch64) Linux support.
Something wrong with your diff. Is it rebased on -next? It doesn't seem
to select HAVE_PTE_SPECIAL and it shouldn't remove other stuff.
--
Catalin
next prev parent reply other threads:[~2012-12-07 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 11:55 [PATCH, REBASED] asm-generic, mm: PTE_SPECIAL cleanup Kirill A. Shutemov
2012-12-07 11:55 ` Kirill A. Shutemov
2012-12-07 14:30 ` Catalin Marinas [this message]
2012-12-07 14:41 ` Kirill A. Shutemov
2012-12-07 15:50 ` Catalin Marinas
2012-12-07 20:35 ` Andrew Morton
2012-12-07 20:35 ` Andrew Morton
2012-12-11 8:53 ` Kirill A. Shutemov
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=20121207143002.GB21233@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.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).