From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Vlastimil Babka <vbabka@suse.cz>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm/vma: Make is_vma_temporary_stack() available for general use
Date: Thu, 27 Feb 2020 05:38:07 +0530 [thread overview]
Message-ID: <8f65781d-1ef0-8314-2baf-586b57a42e9c@arm.com> (raw)
In-Reply-To: <df8b59f9-ccf2-5a40-661e-2bf053b99dac@suse.cz>
On 02/26/2020 07:33 PM, Vlastimil Babka wrote:
> On 2/26/20 5:50 AM, Anshuman Khandual wrote:
>> Currently the declaration and definition for is_vma_temporary_stack() are
>> scattered. Lets make is_vma_temporary_stack() helper available for general
>> use and also drop the declaration from (include/linux/huge_mm.h) which is
>> no longer required. This should not cause any functional change.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-mm@kvack.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>
> The move made it plainly visible that the is_vma_* name differs from all the
> other vma_is_* names. So this is a good chance to unify it?
Yes, we can unify it while moving. Will change.
prev parent reply other threads:[~2020-02-27 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 4:50 [PATCH 0/3] mm/vma: some more minor changes Anshuman Khandual
2020-02-26 4:50 ` [PATCH 1/3] mm/vma: Move VM_NO_KHUGEPAGED into generic header Anshuman Khandual
2020-02-26 11:34 ` Vlastimil Babka
2020-02-27 0:06 ` Anshuman Khandual
2020-02-26 4:50 ` [PATCH 2/3] mm/vma: Make vma_is_foreign() available for general use Anshuman Khandual
2020-02-26 13:59 ` Vlastimil Babka
2020-02-26 4:50 ` [PATCH 3/3] mm/vma: Make is_vma_temporary_stack() " Anshuman Khandual
2020-02-26 14:03 ` Vlastimil Babka
2020-02-27 0:08 ` Anshuman Khandual [this message]
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=8f65781d-1ef0-8314-2baf-586b57a42e9c@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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).