From: Mike Rapoport <rppt@kernel.org>
To: akpm@linux-foundation.org, rongtao@cestc.cn,
Wei Yang <richard.weiyang@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/3] memblock tests: fix build error
Date: Thu, 04 Apr 2024 12:31:30 +0300 [thread overview]
Message-ID: <171222309069.1396621.2828831464457944067.b4-ty@kernel.org> (raw)
In-Reply-To: <20240402132701.29744-1-richard.weiyang@gmail.com>
On Tue, 02 Apr 2024 13:26:58 +0000, Wei Yang wrote:
> Some kernel change break the test build, just fix it.
>
> Wei Yang (3):
> memblock tests: fix undefined reference to `early_pfn_to_nid'
> memblock tests: fix undefined reference to `panic'
> memblock tests: fix undefined reference to `BIT'
>
> [...]
Applied to fixes branch of memblock.git tree, thanks!
[1/3] memblock tests: fix undefined reference to `early_pfn_to_nid'
commit: 7d8ed162e6a92268d4b2b84d364a931216102c8e
[2/3] memblock tests: fix undefined reference to `panic'
commit: e0f5a8e74be88f2476e58b25d3b49a9521bdc4ec
[3/3] memblock tests: fix undefined reference to `BIT'
commit: 592447f6cb3c20d606d6c5d8e6af68e99707b786
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: fixes
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2024-04-04 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:26 Wei Yang
2024-04-02 13:26 ` [PATCH 1/3] memblock tests: fix undefined reference to `early_pfn_to_nid' Wei Yang
2024-04-02 13:27 ` [PATCH 2/3] memblock tests: fix undefined reference to `panic' Wei Yang
2024-04-02 13:27 ` [PATCH 3/3] memblock tests: fix undefined reference to `BIT' Wei Yang
2024-04-02 19:09 ` [PATCH 0/3] memblock tests: fix build error Mike Rapoport
2024-04-03 22:30 ` Andrew Morton
2024-04-04 9:31 ` Mike Rapoport [this message]
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=171222309069.1396621.2828831464457944067.b4-ty@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=rongtao@cestc.cn \
/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