From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Pavel Emelyanov <xemul@parallels.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, criu@openvz.org,
linux-mm@kvack.org, Paul Mackerras <paulus@samba.org>,
Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org, Ingo Molnar <mingo@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
cov@codeaurora.org
Subject: Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook
Date: Mon, 13 Apr 2015 17:27:32 +0200 [thread overview]
Message-ID: <552BE064.4000903@linux.vnet.ibm.com> (raw)
In-Reply-To: <552BD37A.8070505@parallels.com>
On 13/04/2015 16:32, Pavel Emelyanov wrote:
>>>> I initially thought it would be enough to put it into
>>>> <asm-generic/mmu_context.h>, expecting it works as
>>>> <asm-generic/pgtable.h>. But that's not the case.
>>>>
>>>> It probably worth at some point rework all <asm/mmu_context.h> to include
>>>> <asm-generic/mmu_context.h> at the end as we do for <asm/pgtable.h>.
>>>> But that's outside the scope of the patchset, I guess.
>>>>
>>>> I don't see any better candidate for such dummy header. :-/
>>>
>>> Clearly, I'm not confortable with a rewrite of <asm/mmu_context.h> :(
>>>
>>> So what about this patch, is this v3 acceptable ?
>>
>> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>
> Other than the #ifdef thing, the same:
>
> Acked-by: Pavel Emelyanov <xemul@parallels.com>
>
Thanks Kirill and Pavel.
Should I send a new version fixing the spaces around the plus sign ?
Cheers,
Laurent.
next prev parent reply other threads:[~2015-04-13 15:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:56 [RESEND PATCH v3 0/2] Tracking user space vDSO remaping Laurent Dufour
2015-04-13 9:56 ` [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook Laurent Dufour
2015-04-13 11:58 ` Kirill A. Shutemov
2015-04-13 12:41 ` Laurent Dufour
2015-04-13 13:13 ` Kirill A. Shutemov
2015-04-13 13:21 ` Laurent Dufour
2015-04-13 13:35 ` Pavel Emelyanov
2015-04-13 14:02 ` Kirill A. Shutemov
2015-04-13 14:11 ` Laurent Dufour
2015-04-13 14:26 ` Kirill A. Shutemov
2015-04-13 14:32 ` Pavel Emelyanov
2015-04-13 15:27 ` Laurent Dufour [this message]
2015-04-13 20:59 ` Andrew Morton
2015-04-14 9:26 ` Laurent Dufour
2015-04-14 19:38 ` Andrew Morton
2015-04-15 11:57 ` Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 0/3] Tracking user space vDSO remaping Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 1/3] mm: New mm hook framework Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 2/3] mm: New arch_remap hook Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 3/3] powerpc/mm: Tracking vDSO remap Laurent Dufour
2015-04-13 9:56 ` [RESEND PATCH v3 2/2] " Laurent Dufour
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=552BE064.4000903@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cov@codeaurora.org \
--cc=criu@openvz.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=riel@redhat.com \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).