From: gorcunov at gmail.com (Cyrill Gorcunov)
Subject: [PATCH] proc: fix proc-self-map-files selftest for arm
Date: Fri, 12 Oct 2018 00:02:56 +0300 [thread overview]
Message-ID: <20181011210256.GE2401@uranus.lan> (raw)
In-Reply-To: <20181011205601.GA32757@avx2>
On Thu, Oct 11, 2018 at 11:56:01PM +0300, Alexey Dobriyan wrote:
>
> As the comment in the beginning says this test is specifically for addresss 0.
> Maybe it should be ifdeffed with __arm__ then.
Is there some other reason than allocating non-mergable VMA?
WARNING: multiple messages have this Message-ID (diff)
From: gorcunov@gmail.com (Cyrill Gorcunov)
Subject: [PATCH] proc: fix proc-self-map-files selftest for arm
Date: Fri, 12 Oct 2018 00:02:56 +0300 [thread overview]
Message-ID: <20181011210256.GE2401@uranus.lan> (raw)
Message-ID: <20181011210256.L-ws8ckLnDiKGN8XgI-Dl2_jjhXCug3yZ9n6ZH4vbHw@z> (raw)
In-Reply-To: <20181011205601.GA32757@avx2>
On Thu, Oct 11, 2018@11:56:01PM +0300, Alexey Dobriyan wrote:
>
> As the comment in the beginning says this test is specifically for addresss 0.
> Maybe it should be ifdeffed with __arm__ then.
Is there some other reason than allocating non-mergable VMA?
next prev parent reply other threads:[~2018-10-11 21:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:43 [PATCH] proc: fix proc-self-map-files selftest for arm rafael.tinoco
2018-10-11 18:43 ` Rafael David Tinoco
2018-10-11 19:42 ` gorcunov
2018-10-11 19:42 ` Cyrill Gorcunov
2018-10-11 20:56 ` adobriyan
2018-10-11 20:56 ` Alexey Dobriyan
2018-10-11 21:02 ` gorcunov [this message]
2018-10-11 21:02 ` Cyrill Gorcunov
2018-10-11 21:30 ` adobriyan
2018-10-11 21:30 ` Alexey Dobriyan
2018-10-11 22:00 ` gorcunov
2018-10-11 22:00 ` Cyrill Gorcunov
2018-10-15 16:55 ` rafael.tinoco
2018-10-15 16:55 ` Rafael David Tinoco
2018-10-15 17:21 ` gorcunov
2018-10-15 17:21 ` Cyrill Gorcunov
2018-11-08 10:41 ` rafael.tinoco
2018-11-08 10:41 ` Rafael David Tinoco
2018-11-08 11:11 ` gorcunov
2018-11-08 11:11 ` Cyrill Gorcunov
2018-11-09 11:30 ` [PATCH] proc: fix and merge proc-self-map-file tests rafael.tinoco
2018-11-09 11:30 ` Rafael David Tinoco
2018-11-09 11:41 ` gorcunov
2018-11-09 11:41 ` Cyrill Gorcunov
2018-11-09 11:45 ` rafael.tinoco
2018-11-09 11:45 ` Rafael David Tinoco
2018-11-09 11:48 ` gorcunov
2018-11-09 11:48 ` Cyrill Gorcunov
2018-11-09 12:01 ` rafael.tinoco
2018-11-09 12:01 ` Rafael David Tinoco
2018-11-09 18:04 ` gorcunov
2018-11-09 18:04 ` Cyrill Gorcunov
2018-11-09 18:48 ` rafael.tinoco
2018-11-09 18:48 ` Rafael David Tinoco
2018-11-09 19:39 ` gorcunov
2018-11-09 19:39 ` Cyrill Gorcunov
2018-11-10 17:47 ` adobriyan
2018-11-10 17:47 ` Alexey Dobriyan
2018-11-10 17:56 ` rafael.tinoco
2018-11-10 17:56 ` Rafael David Tinoco
2018-11-10 18:49 ` adobriyan
2018-11-10 18:49 ` Alexey Dobriyan
2018-11-11 2:50 ` rafael.tinoco
2018-11-11 2:50 ` Rafael David Tinoco
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=20181011210256.GE2401@uranus.lan \
--to=linux-kselftest@vger.kernel.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