From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org,
oleksiy.avramchenko@sony.com, npiggin@gmail.com,
hch@infradead.org, urezki@gmail.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-vmalloc-use-trace_purge_vmap_area_lazy-event-fix.patch removed from -mm tree
Date: Tue, 08 Nov 2022 17:29:46 -0800 [thread overview]
Message-ID: <20221109012947.7D2CFC433C1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: vmalloc: simplify return boolean expression
has been removed from the -mm tree. Its filename was
mm-vmalloc-use-trace_purge_vmap_area_lazy-event-fix.patch
This patch was dropped because it was folded into mm-vmalloc-use-trace_purge_vmap_area_lazy-event.patch
------------------------------------------------------
From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Subject: mm: vmalloc: simplify return boolean expression
Date: Thu, 20 Oct 2022 14:52:47 +0200
A return expression of the __purge_vmap_area_lazy() function can be
simplified. Basically a boolean expression anyway is converted to boolean
values either to true or false.
Link: https://lkml.kernel.org/r/20221020125247.5053-1-urezki@gmail.com
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Suggested-by: Christoph Hellwig <hch@infradead.org>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/vmalloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/vmalloc.c~mm-vmalloc-use-trace_purge_vmap_area_lazy-event-fix
+++ a/mm/vmalloc.c
@@ -1786,7 +1786,7 @@ static bool __purge_vmap_area_lazy(unsig
out:
trace_purge_vmap_area_lazy(start, end, num_purged_areas);
- return num_purged_areas > 0 ? true:false;
+ return num_purged_areas > 0;
}
/*
_
Patches currently in -mm which might be from urezki@gmail.com are
mm-vmalloc-add-alloc_vmap_area-trace-event.patch
mm-vmalloc-add-purge_vmap_area_lazy-trace-event.patch
mm-vmalloc-add-free_vmap_area_noflush-trace-event.patch
mm-vmalloc-use-trace_alloc_vmap_area-event.patch
mm-vmalloc-use-trace_purge_vmap_area_lazy-event.patch
mm-vmalloc-use-trace_free_vmap_area_noflush-event.patch
vmalloc-add-reviewers-for-vmalloc-code.patch
reply other threads:[~2022-11-09 1:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221109012947.7D2CFC433C1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=oleksiy.avramchenko@sony.com \
--cc=urezki@gmail.com \
--cc=willy@infradead.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.