From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id 391E93858015 for ; Wed, 4 Aug 2021 00:39:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 391E93858015 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=kernel.crashing.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 1740cOls017244; Tue, 3 Aug 2021 19:38:24 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 1740cOxn017243; Tue, 3 Aug 2021 19:38:24 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Tue, 3 Aug 2021 19:38:23 -0500 From: Segher Boessenkool To: will schmidt Cc: Bill Schmidt , gcc-patches@gcc.gnu.org Subject: Re: [PATCH 50/55] rs6000: Update rs6000_builtin_decl Message-ID: <20210804003823.GZ1583@gate.crashing.org> References: <4b66f4b3a0ed196d8c834d3a5ea91998679d1e24.camel@vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4b66f4b3a0ed196d8c834d3a5ea91998679d1e24.camel@vnet.ibm.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, TXREP, T_SPF_HELO_PERMERROR, T_SPF_PERMERROR 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: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2021 00:39:26 -0000 On Tue, Jul 27, 2021 at 04:08:15PM -0500, will schmidt wrote: > On Thu, 2021-06-17 at 10:19 -0500, Bill Schmidt via Gcc-patches wrote: > > 2021-03-05 Bill Schmidt > > > > Hi, > Description could be a bit longer. :-) (Even just a duplicate of the > mail subject to fill the space would prob be fine.) Well, this should completely go away later in the series... Anything named "new" should :-) But some short comment wrt that wouldn't hurt, sure. And there always are a few words too say about any patch, if only to help reviewers :-) Segher