linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
	Pedro Falcato <pfalcato@suse.de>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Jeff Xu <jeffxu@chromium.org>
Subject: Re: [PATCH 3/5] mm/mseal: small cleanups
Date: Mon, 14 Jul 2025 16:39:59 +0200	[thread overview]
Message-ID: <c9c8de37-278b-4d73-97d2-869a7aab3ba3@redhat.com> (raw)
In-Reply-To: <4df6b55c407b5e6890429d4d7cc39e8f28948975.1752497324.git.lorenzo.stoakes@oracle.com>

On 14.07.25 15:00, Lorenzo Stoakes wrote:
> Drop the wholly unnecessary set_vma_sealed() and vma_is_sealed() helpers
> which are used only once, and place VMA_ITERATOR() declarations in the
> correct place.
> 
> No functional change intended.
> 
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---

Acked-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2025-07-14 14:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 13:00 [PATCH 0/5] mseal cleanups Lorenzo Stoakes
2025-07-14 13:00 ` [PATCH 1/5] mm/mseal: always define VM_SEALED Lorenzo Stoakes
2025-07-14 14:31   ` David Hildenbrand
2025-07-14 15:20   ` Pedro Falcato
2025-07-14 15:32   ` Liam R. Howlett
2025-07-14 13:00 ` [PATCH 2/5] mm/mseal: move madvise() logic to mm/madvise.c Lorenzo Stoakes
2025-07-14 14:37   ` David Hildenbrand
2025-07-14 14:56     ` Lorenzo Stoakes
2025-07-14 15:03       ` David Hildenbrand
2025-07-14 15:18         ` Lorenzo Stoakes
2025-07-14 15:24           ` David Hildenbrand
2025-07-14 15:27             ` Lorenzo Stoakes
2025-07-14 15:37               ` David Hildenbrand
2025-07-14 15:31         ` Pedro Falcato
2025-07-14 15:37           ` Lorenzo Stoakes
2025-07-14 15:41           ` David Hildenbrand
2025-07-14 15:45             ` Lorenzo Stoakes
2025-07-14 15:52               ` David Hildenbrand
2025-07-14 16:01                 ` Lorenzo Stoakes
2025-07-14 15:18   ` Pedro Falcato
2025-07-14 15:33   ` Liam R. Howlett
2025-07-14 13:00 ` [PATCH 3/5] mm/mseal: small cleanups Lorenzo Stoakes
2025-07-14 14:39   ` David Hildenbrand [this message]
2025-07-14 15:23   ` Pedro Falcato
2025-07-14 15:33   ` Liam R. Howlett
2025-07-14 13:00 ` [PATCH 4/5] mm/mseal: separate out and simplify VMA gap check Lorenzo Stoakes
2025-07-14 14:41   ` David Hildenbrand
2025-07-14 15:17   ` Pedro Falcato
2025-07-14 15:23     ` Lorenzo Stoakes
2025-07-14 15:25       ` David Hildenbrand
2025-07-14 15:32         ` Lorenzo Stoakes
2025-07-14 15:40           ` Liam R. Howlett
2025-07-14 15:35   ` Liam R. Howlett
2025-07-14 15:40     ` Lorenzo Stoakes
2025-07-14 15:43       ` Liam R. Howlett
2025-07-14 15:47         ` Lorenzo Stoakes
2025-07-14 13:00 ` [PATCH 5/5] mm/mseal: rework mseal apply logic Lorenzo Stoakes
2025-07-14 15:26   ` Pedro Falcato

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=c9c8de37-278b-4d73-97d2-869a7aab3ba3@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=jeffxu@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=pfalcato@suse.de \
    --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).