From: Dmitry Safonov <0x7f454c46@gmail.com>
To: Christopher Covington <cov@codeaurora.org>
Cc: crml <criu@openvz.org>, Will Deacon <will.deacon@arm.com>,
linux-mm@kvack.org, Laurent Dufour <ldufour@linux.vnet.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v2 1/7] mm: Provide generic VDSO unmap and remap functions
Date: Tue, 1 Nov 2016 20:23:54 +0300 [thread overview]
Message-ID: <CAJwJo6Z9qXbYb3RHL89Z2JPJWc6biOt54sWcHXeNwD5dDxQXjQ@mail.gmail.com> (raw)
In-Reply-To: <20161101171101.24704-1-cov@codeaurora.org>
Hi Christopher,
by this moment I got another patch for this. I hope, you don't mind
if I send it concurrently. I haven't sent it yet as I was testing it in qemu.
Thanks,
Dmitry
next prev parent reply other threads:[~2016-11-01 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 17:10 [RFC v2 1/7] mm: Provide generic VDSO unmap and remap functions Christopher Covington
2016-11-01 17:10 ` [RFC v2 2/7] arm: Use generic VDSO unmap and remap Christopher Covington
2016-11-01 17:18 ` Russell King - ARM Linux
2016-11-01 17:10 ` [RFC v2 3/7] arm64: Use unsigned long for VDSO Christopher Covington
2016-11-01 17:10 ` [RFC v2 4/7] arm64: Use generic VDSO unmap and remap functions Christopher Covington
2016-11-01 17:10 ` [RFC v2 5/7] powerpc: Rename context.vdso_base to context.vdso Christopher Covington
[not found] ` <87r36rn8nl.fsf@concordia.ellerman.id.au>
2016-11-04 20:13 ` Will Deacon
2016-11-07 8:01 ` Michael Ellerman
2016-11-01 17:11 ` [RFC v2 6/7] mm/powerpc: Use generic VDSO remap and unmap functions Christopher Covington
2016-11-04 4:59 ` Michael Ellerman
2016-11-07 20:20 ` Laurent Dufour
2016-11-07 23:51 ` Michael Ellerman
2016-11-01 17:23 ` Dmitry Safonov [this message]
2016-11-02 0:23 ` [RFC v2 1/7] mm: Provide generic VDSO unmap and remap functions Christopher Covington
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=CAJwJo6Z9qXbYb3RHL89Z2JPJWc6biOt54sWcHXeNwD5dDxQXjQ@mail.gmail.com \
--to=0x7f454c46@gmail.com \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=criu@openvz.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.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).