From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Rong Tao <rongtao@cestc.cn>, Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock test: compilation fixes
Date: Thu, 21 Sep 2023 08:53:02 +0300 [thread overview]
Message-ID: <20230921055302.GG3303@kernel.org> (raw)
Hi Linus,
The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/fixes-2023-09-21
for you to fetch changes up to 55122e0130e51eb71f5ec62d10525db0468f28e8:
memblock tests: fix warning ‘struct seq_file’ declared inside parameter list (2023-09-14 10:51:28 +0300)
----------------------------------------------------------------
memblock test: compilation fixes
Fix several compilation errors and warnings in memblock tests
----------------------------------------------------------------
Mike Rapoport (IBM) (2):
memblock tests: fix warning: "__ALIGN_KERNEL" redefined
memblock tests: fix warning ‘struct seq_file’ declared inside parameter list
Rong Tao (1):
memblock tests: Fix compilation errors.
tools/include/linux/mm.h | 4 +---
tools/include/linux/seq_file.h | 2 ++
tools/testing/memblock/internal.h | 4 ++++
tools/testing/memblock/mmzone.c | 2 +-
tools/testing/memblock/tests/basic_api.c | 2 +-
tools/testing/memblock/tests/common.h | 1 +
6 files changed, 10 insertions(+), 5 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2023-09-21 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 5:53 Mike Rapoport [this message]
2023-09-21 16:11 ` [GIT PULL] memblock test: compilation fixes 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=20230921055302.GG3303@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rongtao@cestc.cn \
--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.