From: Nathan Chancellor <nathan@kernel.org>
To: WangYuli <wangyuli@uniontech.com>
Cc: masahiroy@kernel.org, nicolas@fjasle.eu,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
chenhuacai@loongson.cn, kernel@xen0n.name, revy@deepin.org,
zhanjun@uniontech.com, niecheng1@uniontech.com,
guanwentao@uniontech.com, chenlinxuan@uniontech.com,
Shiwei Liu <liushiwei@anheng.com.cn>
Subject: Re: [PATCH] kbuild: deb-pkg: add debarch for ARCH=loongarch64
Date: Fri, 28 Feb 2025 21:25:51 -0700 [thread overview]
Message-ID: <20250301042551.GA3565873@ax162> (raw)
In-Reply-To: <DB8BF02DB314013F+20250224182619.1557027-1-wangyuli@uniontech.com>
On Tue, Feb 25, 2025 at 02:26:19AM +0800, WangYuli wrote:
> Fix follow warning when 'make ARCH=loongarch64 bindeb-pkg':
>
> ** ** ** WARNING ** ** **
>
> Your architecture doesn't have its equivalent
> Debian userspace architecture defined!
> Falling back to the current host architecture (loong64).
> Please add support for loongarch64 to ./scripts/package/mkdebian ...
>
> Reported-by: Shiwei Liu <liushiwei@anheng.com.cn>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
> scripts/package/mkdebian | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index b6dd98ca860b..0178000197fe 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -77,6 +77,8 @@ set_debarch() {
> debarch=i386
> fi
> ;;
> + loongarch64)
> + debarch=loong64 ;;
> esac
> if [ -z "$debarch" ]; then
> debarch=$(dpkg-architecture -qDEB_HOST_ARCH)
> --
> 2.47.2
>
next prev parent reply other threads:[~2025-03-01 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:26 [PATCH] kbuild: deb-pkg: add debarch for ARCH=loongarch64 WangYuli
2025-03-01 4:25 ` Nathan Chancellor [this message]
2025-03-03 6:20 ` Masahiro Yamada
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=20250301042551.GA3565873@ax162 \
--to=nathan@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=chenlinxuan@uniontech.com \
--cc=guanwentao@uniontech.com \
--cc=kernel@xen0n.name \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushiwei@anheng.com.cn \
--cc=masahiroy@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=niecheng1@uniontech.com \
--cc=revy@deepin.org \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.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