From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Keith Busch <kbusch@kernel.org>
Subject: [GIT PULL] dmapool updates for 6.4-rc1
Date: Sat, 6 May 2023 10:50:54 -0700 [thread overview]
Message-ID: <20230506105054.0155139b3d3a7f249ead37be@linux-foundation.org> (raw)
Linus, please pull the dmapool updates for 6.4-rc1, thanks.
The following changes since commit 418d5c98319f67b9ae651babea031b5394425c18:
Merge tag 'devicetree-fixes-for-6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2023-05-05 13:27:59 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2023-05-06-10-49
for you to fetch changes up to da9619a30e73b59605ed998bf7bc4359f5c0029a:
dmapool: link blocks across pages (2023-05-06 10:33:38 -0700)
----------------------------------------------------------------
Reinstate the dmapool changes which were accidentally removed by
2d55c16c0c54 ("dmapool: create/destroy cleanup").
----------------------------------------------------------------
Keith Busch (6):
dmapool: move debug code to own functions
dmapool: rearrange page alloc failure handling
dmapool: consolidate page initialization
dmapool: simplify freeing
dmapool: don't memset on free twice
dmapool: link blocks across pages
Tony Battersby (4):
dmapool: remove checks for dev == NULL
dmapool: use sysfs_emit() instead of scnprintf()
dmapool: cleanup integer types
dmapool: speedup DMAPOOL_DEBUG with init_on_alloc
mm/dmapool.c | 407 +++++++++++++++++++++++++++++------------------------------
1 file changed, 202 insertions(+), 205 deletions(-)
next reply other threads:[~2023-05-06 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 17:50 Andrew Morton [this message]
2023-05-06 18:53 ` Linus Torvalds
2023-05-06 19:04 ` Andrew Morton
2023-05-06 18:54 ` pr-tracker-bot
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=20230506105054.0155139b3d3a7f249ead37be@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox