Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4609141ybb; Tue, 14 Apr 2020 10:34:44 -0700 (PDT) X-Google-Smtp-Source: APiQypILkaojrSdPGeow405A1TVJEtKa0u1XDvatQP2BOaUKA8jk0YF9JBc+CPqOMHp2F1+dKWah X-Received: by 2002:a50:b061:: with SMTP id i88mr21901941edd.325.1586885684605; Tue, 14 Apr 2020 10:34:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586885684; cv=none; d=google.com; s=arc-20160816; b=YQndUOmQqLvWpE9BhTozsE9krptg46CmVp5qQfKQ0ZyOzgV+PDWmX/KYTtinQRQYQi Lhy3NbT+OAQa1qcX/3MPUF23/zNWQ21Elj7yZbzOatrD2DybqrvR8GHab0dvLnDvKL4M WYaWrbJqCrznaowIZkZ+eBNa7jq+DUBPIGirMpZ0PV6FmnW8yHzpl5ZEPFieWnzcW5Vk iOaHr0VjE8BaKKP4Ut8MLwqfUC3bMNBRhOF0SNlg1lG6tM/fEUfSHgqfu923O6D8ujws noI8h/Gx1R81mm8Ua0+2xHeWsVtZKfJ3MGPKpDN6SrLds5x+GzXYXxN+UaG0WABnVxrp d1Jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=O+xf0DhJJRRfoOEXDZRgoEB26ommfOZ9QT06HAGckPg=; b=hzL3Mn89y1G1tKclnhfDlJNEbEU2zRl0D6HwftzG2Y/VCp8BMp+ZVlQ4o/q8JcG4ty z16o6c9AzbgJpWZQT7E/weu/S7zBz8ryas2Cz1NaX3EP1LryBImgWTZTxfLrBhMwla7y W5/KB9P4IBXdlaeKphsQQbWr9gTVRrs5YXxhlgIenB3PQ5K//SfeXwdJOIkcaCYb81i+ 8bbzn/jlszK/eaL7wuqXAvI94CTfpJ7qSR20MCFVVPDCbiGZuuL4/AZ8lza5k/6S4b7w j+KbxW6EYyeNcpzGtdynreTP+H4j+NvmR050QlJVy0t0Mr8JW91X3DCvtbCKNVrhDsbD CEWg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ec19si8820053ejb.436.2020.04.14.10.34.20; Tue, 14 Apr 2020 10:34:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2407689AbgDNRdQ (ORCPT + 99 others); Tue, 14 Apr 2020 13:33:16 -0400 Received: from elvis.franken.de ([193.175.24.41]:38894 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732341AbgDNRdN (ORCPT ); Tue, 14 Apr 2020 13:33:13 -0400 Received: from uucp (helo=alpha) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1jOPQo-00026G-00; Tue, 14 Apr 2020 19:33:06 +0200 Received: by alpha.franken.de (Postfix, from userid 1000) id E7E29C010A; Tue, 14 Apr 2020 19:32:08 +0200 (CEST) Date: Tue, 14 Apr 2020 19:32:08 +0200 From: Thomas Bogendoerfer To: Tiezhu Yang Cc: Florian Fainelli , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, Xuefeng Li Subject: Re: [PATCH v2] MIPS: Limit check_bugs32() to affected platform Message-ID: <20200414173208.GA22802@alpha.franken.de> References: <1586488859-18715-1-git-send-email-yangtiezhu@loongson.cn> <181cf95e-c5f6-3899-e8eb-3f8847ec86d9@loongson.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <181cf95e-c5f6-3899-e8eb-3f8847ec86d9@loongson.cn> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 11, 2020 at 10:32:02AM +0800, Tiezhu Yang wrote: > On 04/11/2020 12:25 AM, Florian Fainelli wrote: > > > >On 4/9/2020 8:20 PM, Tiezhu Yang wrote: > >>In the current code, check_bugs32() only handles MIPS32 CPU type CPU_34K, > >>it is better to build and call it on the affected platform. > >> > >>Move check_bugs32() to the new added 34k-bugs32.c to indicate the fact that > >>the code is specific to the 34k CPU, and also add CONFIG_CPU_34K_BUGS32 to > >>control whether or not check the bugs. > >> > >>Signed-off-by: Tiezhu Yang > >This is not a whole lot of code, so moving this to a separate > >translation unit seems a bit heavy handed, also file renames, albeit > >tracked properly by git are always a challenge when doing back ports. > > Hi Florian, > > There exists the following three ways to do it, I'm fine either way, > maybe the first way looks better. Let us wait for the MIPS maintainer > to say what he prefer. > > Hi Thomas, > > What is your opinion? I don't see a reason for doing that at all. The 34K workaround is only compiled in if CONFIG_SYS_HAS_CPU_MIPS32_R2 is defined. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]