Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp2984331iog; Mon, 27 Jun 2022 06:59:49 -0700 (PDT) X-Google-Smtp-Source: AGRyM1snsfsV8d/Exxf382RyCGzbKhwuU4UaFJGHFazdFXydsPqbHTg6nFX4iek1t7V8kK0UfNmK X-Received: by 2002:a17:907:1b1e:b0:6d7:31b0:e821 with SMTP id mp30-20020a1709071b1e00b006d731b0e821mr12627414ejc.334.1656338389170; Mon, 27 Jun 2022 06:59:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656338389; cv=none; d=google.com; s=arc-20160816; b=JMFiE4tyKW0GbVrdaNtIoIVTGK+jLs6Y9RH7jqWjWOPh6JSeIoirBNAQyltJ8pVa93 HkE0zL7G5Ssdlr2yRSgBW+Y+3O6KaSilGipjQEx6QdlGecboVCf0qHwXbGbJ1TPV2m0g YKAGPEXz2oPD7a1M3HY6GLAYcSdQKrnEAQ28F90djQgSwuPZ5Gij4UV7pfM6v/0+/8DE ebrBaUYPjDkrC8RGnhgTBAaPJA6sf/jo+8yTNnvFCfNcRVpnhn24wNdJ78nJiDLMWY5x Fog9jdNgx3L2/97ZpR07VSwPfSwppktAhGJQ//9VZlG0JxzLKMMLwJUHFRXYaomXMafj gLMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:feedback-id:dkim-signature:dkim-signature; bh=VmH1ItcgdR9yLmtHIQblCwoWnqaK8QpzOYYSIYStQo8=; b=P0HQaaLlOTx8EZgoit8CQxzbfbvqhnejq2fUNsN/0WFmUXr8OMw+jPTL4K0A4ye0S/ Ap/RKRVwg2Zzq8lUBYrNri2OqF373IZxMXDJhqDB8QvT2RoHuTjY/Y+Uk13HuHBksZyo F606rssYqi7TdgnkAcbR+94qhOkGwHolmQ4pcXp6h1Wglp0o9Cq79BymHFmPddD2TKje 3Phx/PaToGh+XbUguSTBBWZZb2cCOjfGzfHb/d0oushs1BQQfJ0CG+eysKfmQ7+tscWT A0lz7Ttqbwx6bv8E1HkiZq5FOIgKXW11WzsAY+3nUme/dqhlRhlNgmyGsj1L90AeTO9h 6IsA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sholland.org header.s=fm3 header.b=W6ZgPzFS; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=Jl4m2ts6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j12-20020a170906830c00b006f39e3cc855si10179273ejx.648.2022.06.27.06.59.22; Mon, 27 Jun 2022 06:59:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sholland.org header.s=fm3 header.b=W6ZgPzFS; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=Jl4m2ts6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235727AbiF0NlB (ORCPT + 99 others); Mon, 27 Jun 2022 09:41:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46500 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232562AbiF0Nkq (ORCPT ); Mon, 27 Jun 2022 09:40:46 -0400 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E79065F44; Mon, 27 Jun 2022 06:40:36 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id B7F9E5C00A0; Mon, 27 Jun 2022 09:40:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 27 Jun 2022 09:40:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sholland.org; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1656337233; x= 1656423633; bh=VmH1ItcgdR9yLmtHIQblCwoWnqaK8QpzOYYSIYStQo8=; b=W 6ZgPzFSOSstzSlPkL96ySA528auJvAslWW8vDg5qezyJvV1+N9u6zuEuvAM+oaz+ ff2uSB//o7HZ1x7GS89mc6rF6Lkt6CpWLeykpnkB5Gg+MRmML1s6ug7ngz0huLCp +15HPU6L/ZO5Lm4csRgW1UCzn6Wq7OyZFvDH/bHsmmH/GBuPIFn1Jdbc9Tz3dYsf ilWgpvZimbSueJQ0wkpFMGwlBYdxuUkN6E/KB9KOWLtNSQT4DYRvdTzDHYsGzdA+ v5NJRLgwl9cPGCjryDawOjET0KV3KlA5J532XRMZpt8tB40wLY/XsOYxdkf6USe9 Emo6VoOLgbZj1874ASqfg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1656337233; x= 1656423633; bh=VmH1ItcgdR9yLmtHIQblCwoWnqaK8QpzOYYSIYStQo8=; b=J l4m2ts68BiSTJYOGXO4PS2bCXxr52bv3awRlpRjZkVMApRevrN1swf91dK5VSzbi vlDgC0174yQYu43xulPkY+aNZQ6yxecj/iRNlDm890XFGqRt87oTeOgFBMLrEdu8 N0iglfp90QEV5tuBoGtbZV5QEJjySJLN4Ukd7SHWXtI85+YVsnlA5sptVyFcmsHo qD2JQdBScvSqrLlINFzjSqivKRYMytay9NLIozOzhmWvfB/NZ9LRLDCErDT7VrQv wOp7ar1nUioXyXUzLJo8N5ZuPNx3yE4Q8BaUnijzTMTJhR56vPlSSDINd6ZK3pHr o1yJ7E35bBgs0W8xhXdpQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeghedgieelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvvehfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefurghm uhgvlhcujfholhhlrghnugcuoehsrghmuhgvlhesshhhohhllhgrnhgurdhorhhgqeenuc ggtffrrghtthgvrhhnpefftdevkedvgeekueeutefgteffieelvedukeeuhfehledvhfei tdehudfhudehhfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehsrghmuhgvlhesshhhohhllhgrnhgurdhorhhg X-ME-Proxy: Feedback-ID: i0ad843c9:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 27 Jun 2022 09:40:31 -0400 (EDT) Subject: Re: [PATCH v1 2/3] irqchip/sifive-plic: Name the chip more generically To: Marc Zyngier Cc: Lad Prabhakar , Prabhakar , Sagar Kadam , Paul Walmsley , Palmer Dabbelt , linux-renesas-soc@vger.kernel.org, Guo Ren , Geert Uytterhoeven , Thomas Gleixner , Biju Das , Albert Ou , Krzysztof Kozlowski , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org References: <20220627051257.38543-1-samuel@sholland.org> <20220627051257.38543-3-samuel@sholland.org> <20511a05f39408c8ffbcc98923c4abd2@kernel.org> From: Samuel Holland Message-ID: Date: Mon, 27 Jun 2022 08:40:30 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20511a05f39408c8ffbcc98923c4abd2@kernel.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/27/22 2:11 AM, Marc Zyngier wrote: > On 2022-06-27 06:12, Samuel Holland wrote: >> The interface for SiFive's PLIC was adopted and clarified by RISC-V as >> the standard PLIC interface. Now that several PLIC implementations by >> different vendors share this same interface, it is somewhat misleading >> to report "SiFive PLIC" to userspace, when no SiFive hardware may be >> present. This is especially the case when some implementations are >> subtly incompatible with the binding and behavior of the SiFive PLIC, >> yet are similar enough to share a driver. > > Too late. This is ABI, and not changing, exactly because userspace > sees it. That makes sense. I will drop this patch. Regards, Samuel