All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
	Jinyu Tang <tjytimi@163.com>,
	Liu Xinpeng <liuxp11@chinatelecom.cn>,
	Ma Wupeng <mawupeng1@huawei.com>, Mike Rapoport <rppt@kernel.org>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Rebecca Mckeever <remckee0@gmail.com>,
	Shaoqin Huang <shaoqin.huang@intel.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock updates for v5.20
Date: Tue, 9 Aug 2022 10:25:07 +0300	[thread overview]
Message-ID: <YvIL0wn1WTDxjFVr@kernel.org> (raw)

Hi Linus,

The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:

  Linux 5.19-rc4 (2022-06-26 14:22:10 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v5.20-rc1

for you to fetch changes up to 04d9490986d1e04a38db88276115e6b3c9ec3faa:

  memblock test: Modify the obsolete description in README (2022-07-30 11:46:49 +0300)

----------------------------------------------------------------
memblock updates for v5.20

* An optimization in memblock_add_range() to reduce array traversals
* Improvements to the memblock test suite

----------------------------------------------------------------
Jinyu Tang (1):
      memblock: avoid some repeat when add new range

Liu Xinpeng (1):
      memblock tests: fix compilation errors

Rebecca Mckeever (5):
      memblock tests: Makefile: add arguments to control verbosity
      memblock tests: add verbose output to memblock tests
      memblock tests: set memblock_debug to enable memblock_dbg() messages
      memblock tests: remove completed TODO items
      memblock tests: change build options to run-time options

Shaoqin Huang (1):
      memblock test: Modify the obsolete description in README

 mm/memblock.c                                    |  11 +
 tools/testing/memblock/Makefile                  |   3 +-
 tools/testing/memblock/README                    |  17 +-
 tools/testing/memblock/TODO                      |  14 +-
 tools/testing/memblock/internal.h                |  11 +
 tools/testing/memblock/linux/memory_hotplug.h    |   8 +-
 tools/testing/memblock/main.c                    |   2 +
 tools/testing/memblock/scripts/Makefile.include  |  10 +-
 tools/testing/memblock/tests/alloc_api.c         | 225 ++++++++++-----
 tools/testing/memblock/tests/alloc_helpers_api.c | 129 ++++++---
 tools/testing/memblock/tests/alloc_nid_api.c     | 351 +++++++++++++++--------
 tools/testing/memblock/tests/basic_api.c         | 337 +++++++++++++++-------
 tools/testing/memblock/tests/common.c            | 118 ++++++++
 tools/testing/memblock/tests/common.h            |  54 ++++
 14 files changed, 920 insertions(+), 370 deletions(-)

-- 
Sincerely yours,
Mike.


             reply	other threads:[~2022-08-09  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09  7:25 Mike Rapoport [this message]
2022-08-09 17:02 ` [GIT PULL] memblock updates for v5.20 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=YvIL0wn1WTDxjFVr@kernel.org \
    --to=rppt@kernel.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuxp11@chinatelecom.cn \
    --cc=mawupeng1@huawei.com \
    --cc=remckee0@gmail.com \
    --cc=rppt@linux.ibm.com \
    --cc=shaoqin.huang@intel.com \
    --cc=tjytimi@163.com \
    --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 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.