From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, "kernel test robot" <lkp@intel.com>,
"Dengcheng Zhu" <dzhu@wavecomp.com>,
"John Crispin" <john@phrozen.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Steven J. Hill" <Steven.Hill@imgtec.com>,
"Qais Yousef" <Qais.Yousef@imgtec.com>,
"Yang Yingliang" <yangyingliang@huawei.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"James Hogan" <jhogan@kernel.org>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: vpe-mt: drop physical_memsize
Date: Mon, 20 Feb 2023 15:12:36 +0100 [thread overview]
Message-ID: <20230220141236.GA9547@alpha.franken.de> (raw)
In-Reply-To: <20230219231525.21542-1-rdunlap@infradead.org>
On Sun, Feb 19, 2023 at 03:15:25PM -0800, Randy Dunlap wrote:
> When neither LANTIQ nor MIPS_MALTA is set, 'physical_memsize' is not
> declared. This causes the build to fail with:
>
> mips-linux-ld: arch/mips/kernel/vpe-mt.o: in function `vpe_run':
> arch/mips/kernel/vpe-mt.c:(.text.vpe_run+0x280): undefined reference to `physical_memsize'
>
> LANTIQ is not using 'physical_memsize' and MIPS_MALTA's use of it is
> self-contained in mti-malta/malta-dtshim.c.
> Use of physical_memsize in vpe-mt.c appears to be unused, so eliminate
> this loader mode completely and require VPE programs to be compiled with
> DFLT_STACK_SIZE and DFLT_HEAP_SIZE defined.
>
> Fixes: 9050d50e2244 ("MIPS: lantiq: Set physical_memsize")
> Fixes: 1a2a6d7e8816 ("MIPS: APRP: Split VPE loader into separate files.")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/all/202302030625.2g3E98sY-lkp@intel.com/
> Cc: Dengcheng Zhu <dzhu@wavecomp.com>
> Cc: John Crispin <john@phrozen.org>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: Philippe Mathieu-Daudé <philmd@linaro.org>
> Cc: "Steven J. Hill" <Steven.Hill@imgtec.com>
> Cc: Qais Yousef <Qais.Yousef@imgtec.com>
> Cc: Yang Yingliang <yangyingliang@huawei.com>
> Cc: Hauke Mehrtens <hauke@hauke-m.de>
> Cc: James Hogan <jhogan@kernel.org>
> Cc: linux-mips@vger.kernel.org
> ---
> v2 changes: instead of providing a default physical_memsize of 0, which
> is not correct for MIPS_MALTA, just eliminate its use in vpe-mt.c.
>
> arch/mips/include/asm/vpe.h | 1 -
> arch/mips/kernel/vpe-mt.c | 7 +++----
> arch/mips/lantiq/prom.c | 6 ------
> 3 files changed, 3 insertions(+), 11 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-02-20 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 23:15 [PATCH v2] MIPS: vpe-mt: drop physical_memsize Randy Dunlap
2023-02-20 14:12 ` Thomas Bogendoerfer [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=20230220141236.GA9547@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Qais.Yousef@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=dzhu@wavecomp.com \
--cc=hauke@hauke-m.de \
--cc=jhogan@kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philmd@linaro.org \
--cc=rdunlap@infradead.org \
--cc=yangyingliang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).