From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 392B9ECE58D for ; Thu, 17 Oct 2019 17:19:32 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 11EA921D7D for ; Thu, 17 Oct 2019 17:19:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="LqsZZ7eB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 11EA921D7D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NxtiJYPHws3Vry03pavlXiB7U94oXGxNZ/WaXdoo5xA=; b=LqsZZ7eBHg8pRK TXl1modzSrgy44rVjX1qkGEyS51GmqU/NzYYVGXj47VQ11VQRq821iQlzbnM8iBWvd1Qoazno5eE+ ZrKVDSHBG/Z/vBR1qAQzuoB+BcjPs4R3gWs5wlwfTw1RnoDkGYxEIdSojx7dMvbAk1HJOqFg2k/pU bgVxWS6ZC6djKKmGOHapxkOPwfcu7RuY+3CHdUk6fWyJmqBaHIVnT8taGMKlHvZ8QIgGogbku38ot TCYbH9UFCXtlEeUpI0cGOqRNTMwi0bo7zMRZJcV5EQ4Fzt24BjkKh3OCYeDMMAEMDkNSHjKRI5mmX 6v7i9JG/AbBDzjDfQ1JQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iL9Qw-0000Qe-Lz; Thu, 17 Oct 2019 17:19:30 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iL9Qu-0000Q2-KV for linux-riscv@lists.infradead.org; Thu, 17 Oct 2019 17:19:29 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id B322368BE1; Thu, 17 Oct 2019 19:19:24 +0200 (CEST) Date: Thu, 17 Oct 2019 19:19:24 +0200 From: Christoph Hellwig To: Mauro Carvalho Chehab Subject: Re: [PATCH] riscv: move sifive_l2_cache.c to drivers/soc Message-ID: <20191017171924.GA10928@lst.de> References: <20190818082935.14869-1-hch@lst.de> <20190819060904.GA4841@zn.tnic> <20190819062619.GA20211@lst.de> <20190822062635.00f6e507@coco.lan> <20190927225304.GA18456@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190927225304.GA18456@lst.de> User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191017_101928_823813_424C08FC X-CRM114-Status: GOOD ( 13.61 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: palmer@sifive.com, linux-kernel@vger.kernel.org, Yash Shah , Borislav Petkov , paul.walmsley@sifive.com, linux-riscv@lists.infradead.org, Christoph Hellwig , linux-edac@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org Mauro, can you Ack this patch? On Sat, Sep 28, 2019 at 12:53:04AM +0200, Christoph Hellwig wrote: > > > well enough myself, and I really need to get this code out of the > > > forced on RISC-V codebase as some SOCs I'm working with simply don't > > > have the memory for it.. > > > > > > So unless someone signs up to do a per-IP block edac drivers instead > > > very quickly I'd still like to see something like this go into 5.4 > > > for now. > > > > I'm wandering if we should at least add an entry for this one at > > MAINTAINERS, pointing it to the EDAC mailing list. Something like: > > Sounds fine. Can you also ACK the patch with that, as Paul mention > in another thread he wants an EDAC ACK for it. ---end quoted text--- _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv