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=-1.0 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 4241 invoked from network); 3 Apr 2023 15:44:51 -0000
Received: from second.openwall.net (193.110.157.125)
  by inbox.vuxu.org with ESMTPUTF8; 3 Apr 2023 15:44:51 -0000
Received: (qmail 25900 invoked by uid 550); 3 Apr 2023 15:44:48 -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 25868 invoked from network); 3 Apr 2023 15:44:48 -0000
Date: Mon, 3 Apr 2023 17:44:35 +0200
From: Szabolcs Nagy <nsz@port70.net>
To: Rich Felker <dalias@libc.org>
Cc: =?utf-8?B?546L5rSq5Lqu?= <wanghongliang@loongson.cn>,
	musl@lists.openwall.com
Message-ID: <20230403154435.GH3630668@port70.net>
Mail-Followup-To: Rich Felker <dalias@libc.org>,
	=?utf-8?B?546L5rSq5Lqu?= <wanghongliang@loongson.cn>,
	musl@lists.openwall.com
References: <c434ca80-98ec-fb96-cda8-9baf395e78f0@loongson.cn>
 <d70b0b48-b4bf-293b-24eb-1eadfcb90f34@loongson.cn>
 <ab79680f258efa196b5dab4262c8bccc@dereferenced.org>
 <20230129170407.GL4163@brightrain.aerifal.cx>
 <7c77f6d5-7f42-f3a9-af81-99a251780d19@loongson.cn>
 <20230216231336.GW4163@brightrain.aerifal.cx>
 <2775a5e6-1fc0-e542-47ea-e90170053654@loongson.cn>
 <00d245b2-c0b5-9978-7f7b-9d5aa5df6137@loongson.cn>
 <20230403133523.GG3630668@port70.net>
 <20230403144248.GE4163@brightrain.aerifal.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20230403144248.GE4163@brightrain.aerifal.cx>
Subject: Re: [musl] add loongarch64 port v6.

* Rich Felker <dalias@libc.org> [2023-04-03 10:42:49 -0400]:

> On Mon, Apr 03, 2023 at 03:35:23PM +0200, Szabolcs Nagy wrote:
> > * =E7=8E=8B=E6=B4=AA=E4=BA=AE <wanghongliang@loongson.cn> [2023-03-17 1=
6:41:26 +0800]:
> > > Hi, Rich
> > >=20
> > > Do I need to do any other work with this patch v6=EF=BC=9F
> >=20
> > where is v6?
> >=20
> > i only see v5 patch on the list
>=20
> The v6 was just sent as a link to git repo, I think. And indeed now I
> need to make sure I can find the copy I grabbed to look at last time,
> or else look over it again to ensure this is still correct and still
> what I reviewed. This is why patches should always be sent as
> attachments (thus immutable) not links.
>=20
> I'm trying to wrap up the release now and expect I will apply this
> (with the minor formatting fixes I promised I could make myself at
> merge time) right after release.

i was asking because of this glibc patch:
https://sourceware.org/pipermail/libc-alpha/2023-April/146897.html

i dont understand that change (loongarch is in glibc since 2.36 release).