From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Eric DeVolder <eric_devolder@yahoo.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [akpm-mm:mm-unstable 25/192] loongarch64-linux-ld: kexec_core.c:undefined reference to `machine_kexec'
Date: Fri, 1 Dec 2023 07:09:02 +0800 [thread overview]
Message-ID: <ZWkWDg41Q5eGuNU4@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20231130085335.09e1db227e3a99e1f70e7748@linux-foundation.org>
On 11/30/23 at 08:53am, Andrew Morton wrote:
> On Thu, 30 Nov 2023 16:43:00 +0800 Baoquan He <bhe@redhat.com> wrote:
>
> > There are several places in m68k, mips, sh architecture which have the
> > similar issue. Would you prefer one patch to contain them all or
> > separate patches for each architecture's fix?
>
> Doesn't matter much. I guess a single patch would save some electrons.
Sure, will post one patch to include them all. Thanks.
prev parent reply other threads:[~2023-11-30 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 4:02 [akpm-mm:mm-unstable 25/192] loongarch64-linux-ld: kexec_core.c:undefined reference to `machine_kexec' kernel test robot
2023-11-30 8:43 ` Baoquan He
2023-11-30 16:53 ` Andrew Morton
2023-11-30 23:09 ` Baoquan He [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=ZWkWDg41Q5eGuNU4@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=eric_devolder@yahoo.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.