From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org,
tonyb@cybernetics.com, hch@lst.de, kbusch@kernel.org,
akpm@linux-foundation.org
Subject: [merged mm-stable] dmapool-consolidate-page-initialization.patch removed from -mm tree
Date: Fri, 05 May 2023 15:39:05 -0700 [thread overview]
Message-ID: <20230505223906.6F806C433D2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: dmapool: consolidate page initialization
has been removed from the -mm tree. Its filename was
dmapool-consolidate-page-initialization.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Keith Busch <kbusch@kernel.org>
Subject: dmapool: consolidate page initialization
Date: Thu, 26 Jan 2023 13:51:21 -0800
Various fields of the dma pool are set in different places. Move it all
to one function.
Link: https://lkml.kernel.org/r/20230126215125.4069751-9-kbusch@meta.com
Fixes: 2d55c16c0c54 ("dmapool: create/destroy cleanup")
Signed-off-by: Keith Busch <kbusch@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Tony Battersby <tonyb@cybernetics.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/dmapool.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--- a/mm/dmapool.c~dmapool-consolidate-page-initialization
+++ a/mm/dmapool.c
@@ -274,6 +274,9 @@ static void pool_initialise_page(struct
unsigned int offset = 0;
unsigned int next_boundary = pool->boundary;
+ pool_init_page(pool, page);
+ page->in_use = 0;
+ page->offset = 0;
do {
unsigned int next = offset + pool->size;
if (unlikely((next + pool->size) >= next_boundary)) {
@@ -300,11 +303,7 @@ static struct dma_page *pool_alloc_page(
return NULL;
}
- pool_init_page(pool, page);
pool_initialise_page(pool, page);
- page->in_use = 0;
- page->offset = 0;
-
return page;
}
_
Patches currently in -mm which might be from kbusch@kernel.org are
next reply other threads:[~2023-05-05 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 22:39 Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-06 2:44 [merged mm-stable] dmapool-consolidate-page-initialization.patch removed from -mm tree Andrew Morton
2023-02-26 23:48 Andrew Morton
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=20230505223906.6F806C433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tonyb@cybernetics.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.