From: Alexey Dobriyan <adobriyan@gmail.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, "David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC 3/3] mm/vma: Introduce some more VMA flag wrappers
Date: Tue, 10 Mar 2020 20:26:09 +0000 [thread overview]
Message-ID: <20200310202609.GA6287@avx2> (raw)
In-Reply-To: <ce7dd2ac-26e8-d83c-46d0-0c61609be417@arm.com>
On Tue, Mar 03, 2020 at 02:43:21PM +0530, Anshuman Khandual wrote:
> On 03/03/2020 12:04 PM, Hugh Dickins wrote:
> > On Mon, 2 Mar 2020, Anshuman Khandual wrote:
> >> vma_is_dontdump()
> >> vma_is_noreserve()
> >> vma_is_special()
> >> vma_is_locked()
> >> vma_is_mergeable()
> >> vma_is_softdirty()
> >> vma_is_thp()
> >> vma_is_nothp()
> > Improved readability? Not to my eyes.
>
> As mentioned before, I dont feel strongly about patch 3/3 and will drop.
Should be "const struct vm_area_struct *" anyway.
WARNING: multiple messages have this Message-ID (diff)
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, "David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC 3/3] mm/vma: Introduce some more VMA flag wrappers
Date: Tue, 10 Mar 2020 23:26:09 +0300 [thread overview]
Message-ID: <20200310202609.GA6287@avx2> (raw)
In-Reply-To: <ce7dd2ac-26e8-d83c-46d0-0c61609be417@arm.com>
On Tue, Mar 03, 2020 at 02:43:21PM +0530, Anshuman Khandual wrote:
> On 03/03/2020 12:04 PM, Hugh Dickins wrote:
> > On Mon, 2 Mar 2020, Anshuman Khandual wrote:
> >> vma_is_dontdump()
> >> vma_is_noreserve()
> >> vma_is_special()
> >> vma_is_locked()
> >> vma_is_mergeable()
> >> vma_is_softdirty()
> >> vma_is_thp()
> >> vma_is_nothp()
> > Improved readability? Not to my eyes.
>
> As mentioned before, I dont feel strongly about patch 3/3 and will drop.
Should be "const struct vm_area_struct *" anyway.
next prev parent reply other threads:[~2020-03-10 20:26 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 6:47 [RFC 0/3] mm/vma: some new flags and helpers Anshuman Khandual
2020-03-02 6:59 ` Anshuman Khandual
2020-03-02 6:47 ` [OpenRISC] " Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` [RFC 1/3] mm/vma: Define a default value for VM_DATA_DEFAULT_FLAGS Anshuman Khandual
2020-03-02 6:59 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` [OpenRISC] " Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-02 8:22 ` [OpenRISC] " Geert Uytterhoeven
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-02 8:22 ` Geert Uytterhoeven
2020-03-03 17:25 ` Vlastimil Babka
2020-03-03 17:25 ` Vlastimil Babka
2020-03-03 17:25 ` Vlastimil Babka
2020-03-03 17:25 ` [OpenRISC] " Vlastimil Babka
2020-03-03 17:25 ` Vlastimil Babka
2020-03-03 17:25 ` Vlastimil Babka
2020-03-03 17:25 ` Vlastimil Babka
2020-03-03 17:25 ` Vlastimil Babka
2020-03-04 5:19 ` Anshuman Khandual
2020-03-04 5:31 ` Anshuman Khandual
2020-03-04 5:19 ` Anshuman Khandual
2020-03-04 5:19 ` Anshuman Khandual
2020-03-04 5:19 ` [OpenRISC] " Anshuman Khandual
2020-03-04 5:19 ` Anshuman Khandual
2020-03-04 5:19 ` Anshuman Khandual
2020-03-04 5:19 ` Anshuman Khandual
2020-03-02 6:47 ` [RFC 2/3] mm/vma: Introduce VM_ACCESS_FLAGS Anshuman Khandual
2020-03-02 6:59 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-02 6:47 ` Anshuman Khandual
2020-03-03 17:48 ` Vlastimil Babka
2020-03-03 17:48 ` Vlastimil Babka
2020-03-03 17:48 ` Vlastimil Babka
2020-03-03 17:48 ` Vlastimil Babka
2020-03-04 5:52 ` Anshuman Khandual
2020-03-04 5:52 ` Anshuman Khandual
2020-03-04 5:52 ` Anshuman Khandual
2020-03-04 5:52 ` Anshuman Khandual
2020-03-02 6:47 ` [RFC 3/3] mm/vma: Introduce some more VMA flag wrappers Anshuman Khandual
2020-03-02 6:59 ` Anshuman Khandual
2020-03-03 6:34 ` Hugh Dickins
2020-03-03 6:34 ` Hugh Dickins
2020-03-03 9:13 ` Anshuman Khandual
2020-03-03 9:25 ` Anshuman Khandual
2020-03-10 20:26 ` Alexey Dobriyan [this message]
2020-03-10 20:26 ` Alexey Dobriyan
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=20200310202609.GA6287@avx2 \
--to=adobriyan@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=davem@davemloft.net \
--cc=hughd@google.com \
--cc=jolsa@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.