From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <macro@orcam.me.uk>
Received: from angie.orcam.me.uk (angie.orcam.me.uk [78.133.224.34])
 by sourceware.org (Postfix) with ESMTP id 2B61E3857340
 for <gdb-patches@sourceware.org>; Mon, 11 Apr 2022 15:32:13 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2B61E3857340
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=orcam.me.uk
Authentication-Results: sourceware.org; spf=none smtp.mailfrom=orcam.me.uk
Received: by angie.orcam.me.uk (Postfix, from userid 500)
 id B544492009C; Mon, 11 Apr 2022 17:32:11 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by angie.orcam.me.uk (Postfix) with ESMTP id AF4C792009B;
 Mon, 11 Apr 2022 16:32:11 +0100 (BST)
Date: Mon, 11 Apr 2022 16:32:11 +0100 (BST)
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Youling Tang <tangyouling@loongson.cn>
cc: Richard Sandiford <richard.sandiford@arm.com>, 
 Andrew Burgess <aburgess@redhat.com>, Lancelot SIX <lsix@lancelotsix.com>, 
 gdb-patches@sourceware.org
Subject: Re: [COMMITTED PATCH v2] gdb: mips: Fix the handling of complex type
 of function return value
In-Reply-To: <9e315c60-54e3-afdf-f28e-008854ffbe06@loongson.cn>
Message-ID: <alpine.DEB.2.21.2204111621240.9383@angie.orcam.me.uk>
References: <1647406106-25723-1-git-send-email-tangyouling@loongson.cn>
 <20220316084248.m5m2et3njtngeoge@Plymouth>
 <ebead02d-15ed-344c-c2b3-a85e89038c08@loongson.cn>
 <877d8uuop8.fsf@redhat.com>
 <alpine.DEB.2.21.2203161819070.24248@angie.orcam.me.uk>
 <a573a55e-00f2-fc76-aee4-c4432bdf253c@loongson.cn>
 <alpine.DEB.2.21.2204042138380.47162@angie.orcam.me.uk>
 <9e315c60-54e3-afdf-f28e-008854ffbe06@loongson.cn>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Spam-Status: No, score=-1162.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_INFOUSMEBIZ, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gdb-patches@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2022 15:32:14 -0000

Hi Youling,

> >   I cannot see you listed in MAINTAINERS, but your original change only had
> > a legally insignificant amount of changes, so I have now committed this
> > updated version.  However for the sake of any future submissions you may
> > make can you please explain your current FSF copyright assignment status?
> I am working for Loongson Technology Corporation Limited.
> Loongson has signed the copyright assignment.
> Loongson GNU ANY is RT 1604586.

 OK, this sounds good.

> Can I add to the MAINTAINERS list for the convenience of submitting code
> later?

 You'll need to request repository write access first and have that 
sponsored by a general maintainer.  You'll be able to make such a request 
once you have got one or a couple of good changes accepted.  At that point 
you'll add yourself to MAINTAINERS as your first change to the repository.

  Maciej