From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 554F33854167 for ; Fri, 21 Oct 2022 10:47:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 554F33854167 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666349242; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=f8in749sv4R/GuuG0Sn9yl88acCjt/LlT4o8nALF4Ao=; b=by8M9RlSfAARXzJz3x5Vu/DLj1+2gyzpunoIq7omgmoZUKEm5UzaR+/0n9xclKx06fvYoM bKIY8vmfg45AHlXkWFXH4hucqCLJ09nv6OCqRxXRyPIo5+SuxjMrn6DC6RdICNbvqI71cg EmcMH7fJkHArHtl5gRF7NJwGExoitfo= Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-351-_0oo-m63N663RiBYMne8Kw-1; Fri, 21 Oct 2022 06:47:20 -0400 X-MC-Unique: _0oo-m63N663RiBYMne8Kw-1 Received: by mail-qt1-f199.google.com with SMTP id k12-20020ac8474c000000b0039cdd680ccaso2227114qtp.1 for ; Fri, 21 Oct 2022 03:47:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:subject:from:references:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=f8in749sv4R/GuuG0Sn9yl88acCjt/LlT4o8nALF4Ao=; b=7Kfd1lKn46d4bGuaeTnRZIhcGL0bR7/b/JsMVrq6h06jgqp8UaNmTP4I88uWPYGpOA j+bOXJHPQhj4XRcV8PYupkU8PwCIB9548C+KuKDxOJE3srmz03VfkibGWAB7HnA83FMc SLJ1LhkPsXdgOw3oX51DnMwXXw6DgosWfp3ftabAJbLqPvNVY8obzas7CBnZ3XH67/eg ruvWtMvztLWTqx+FMh5ts9wz8ULlBzUgWAD+6yHfRzfUDQ9LuvPxMhuIp100Yc9HuGXE 3MrXGm7gMnD+GoeGCQc0pyDji1t12oNJ5W3qdBmzus37PbogcEJulwehEq7ijs9Pcfbv YoHg== X-Gm-Message-State: ACrzQf0WbmiFa0sJNiU5prfmy3fb32Une1d0uIqhVhg7/UrE3UPOUsI6 ifv3TDhaY67yjoC7TUpcYjsnHClqhve4LK18CzIY5dfFa622EuY61dqzf41vpDTCBKI93P3y0+5 GyS0sEQKeiOlQmX/OHg== X-Received: by 2002:ac8:5988:0:b0:39a:dee7:ba40 with SMTP id e8-20020ac85988000000b0039adee7ba40mr15440039qte.635.1666349240442; Fri, 21 Oct 2022 03:47:20 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5YMqc6WzeCzPBMnQfmXzQ0zEetm8/j+SRVqcCbsLAzIe7Etj4vlru1m+OU3kimAyon6tUyww== X-Received: by 2002:ac8:5988:0:b0:39a:dee7:ba40 with SMTP id e8-20020ac85988000000b0039adee7ba40mr15440026qte.635.1666349240216; Fri, 21 Oct 2022 03:47:20 -0700 (PDT) Received: from [192.168.1.18] (adsl-164-85.freeuk.com. [80.168.164.85]) by smtp.gmail.com with ESMTPSA id y9-20020a37f609000000b006ce7cd81359sm9076680qkj.110.2022.10.21.03.47.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Oct 2022 03:47:19 -0700 (PDT) Message-ID: <0deaab53-e106-c5e6-6a3a-5f9bbe32af04@redhat.com> Date: Fri, 21 Oct 2022 11:47:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 To: David Guillen , binutils@sourceware.org References: From: Nick Clifton Subject: Re: Upstream PSP support in binutils In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-GB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi David, > I'm reaching out to know how much interest there'd be to add upstream > support in binutils for the Sony PSP CPU. Before patches are crafted and > tests are written, I'd like to know if this is something that you guys > would consider merging. I'd be doing the work but you would need to help > reviewing and merging it of course :) Of course. :-) The short answer is "yes", but with a caveat. Or two. The first being that someone needs to volunteer to act as a maintainer for the port. They need to be willing to read the mailing list, handle PSP specific bug reports, answer questions about the port, and generally make sure that it carries on working as the years progress. The other caveat is that ideally the copyright for the patches should be assigned to the FSF. (Strictly speaking we are now accepting DCO signed contributions as well, but for a new port I would feel happier with a copyright assignment). Plus they should follow the GNU Coding Standards, not break other ports, have a testsuite, and all the usual things for a contribution to the GNU Binutils. Cheers Nick