From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 21947 invoked from network); 11 May 2022 15:57:44 -0000
Received: from mother.openwall.net (195.42.179.200)
  by inbox.vuxu.org with ESMTPUTF8; 11 May 2022 15:57:44 -0000
Received: (qmail 17968 invoked by uid 550); 11 May 2022 15:57:41 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 17936 invoked from network); 11 May 2022 15:57:40 -0000
Date: Wed, 11 May 2022 09:37:07 -0400
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Message-ID: <20220511133707.GF7074@brightrain.aerifal.cx>
References: <c6c18c0d-7244-2cb2-a99c-a520a88bc704@loongson.cn>
 <f9d751a1-1ba4-298c-f4bb-a54226674dc2@loongson.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <f9d751a1-1ba4-298c-f4bb-a54226674dc2@loongson.cn>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] Re: add loongarch64 port v3

On Mon, May 09, 2022 at 09:34:59AM +0800, 王洪亮 wrote:
> 
> 在 2022/5/5 上午11:21, 王洪亮 写道:
> >Hi,
> >
> >I published loongarch64 port v3 in
> >https://github.com/loongson/musl/tree/loongarch-v2.0.
> >
> >fixed two problem:
> >
> >1.use __NR_clone3 in  __clone().
> >
> >2.remove __NR_fstat and __NR_newfstatat.
> >
> >please code review if there are any other problems ? thanks.
> >
> >
> >Hongliang Wang.
> >
> Hi,
> 
> this port has any other problems need to fix?

I'm at least waiting for confirmation from the kernel side that
everything is okay with syscall usage to move forward. I'll try to
look over the rest again soon to check that there are no remaining
issues.