From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
rongtao@cestc.cn, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/3] memblock tests: fix build error
Date: Wed, 3 Apr 2024 15:30:26 -0700 [thread overview]
Message-ID: <20240403153026.67f05e557304c97078a3e13d@linux-foundation.org> (raw)
In-Reply-To: <ZgxX-5Eu4MU_SEqV@kernel.org>
On Tue, 2 Apr 2024 22:09:47 +0300 Mike Rapoport <rppt@kernel.org> wrote:
> On Tue, Apr 02, 2024 at 01:26:58PM +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'
> >
> > include/linux/gfp_types.h | 2 ++
> > tools/include/linux/kernel.h | 1 +
> > tools/include/linux/mm.h | 5 +++++
> > tools/include/linux/panic.h | 19 +++++++++++++++++++
> > 4 files changed, 27 insertions(+)
> > create mode 100644 tools/include/linux/panic.h
>
> Andrew,
>
> I can take these via memblock tree, what is your preference?
I'm seeing no conflicts at this time, so go for it.
next prev parent reply other threads:[~2024-04-03 22:30 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 [this message]
2024-04-04 9:31 ` Mike Rapoport
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=20240403153026.67f05e557304c97078a3e13d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=rongtao@cestc.cn \
--cc=rppt@kernel.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