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=-5.3 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 806A2C433E0 for ; Thu, 23 Jul 2020 09:53:33 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 4CADE20709 for ; Thu, 23 Jul 2020 09:53:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="cx/2jV0D" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4CADE20709 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.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=gRnVRIVIKFnQoR8JtnxgRLobVk4Rq9y3vetEAvzjsH0=; b=cx/2jV0DQVgSmWo1FkPPfjeKC g/V9fmdE+YdhCLqyZfruGtngjBgr3BH1FYoN4fHZVb+tut14dtHdSncy7Q17LPzhYkqHtpH8NbUrs SEXuFcVZuM1TigdBP69XsH0TODNr1Mtu3SSnnd4Ni3gGYVHfqAWn41wtrFhF7DxMAk5m0V1Geq1RX Mb1yly8ShCw2zarxH6LqlCsMrrpWS7dF+3hpV1yG9xiPue7ExMRSupJ7P4Rkab5+KI2cvJTXPY3BU 1KKPiKlRzCNrMgTlYPNUlK7g7ty1o2UP0ljbRWRXhUAuOrOtU6TDurf80SllHAGswU4XJLPWOsNaq RIMp16g7Q==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jyXth-0001hK-78; Thu, 23 Jul 2020 09:52:17 +0000 Received: from mail-ej1-f68.google.com ([209.85.218.68]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jyXte-0001gk-JR; Thu, 23 Jul 2020 09:52:15 +0000 Received: by mail-ej1-f68.google.com with SMTP id ga4so5675667ejb.11; Thu, 23 Jul 2020 02:52:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=puQQ+kEDvp4d2ixkulEX0wUmGQuAZ6n3qHTJVU/5Rzc=; b=EBn7cNz9TC//QL0mldmPioHfZm/A4vF5lhdDUQauLOYUJa+9K9yfpIJZuJ2cQcEu7F fGI9gpYMfzUm4OdsRQMsGsg9iKAkAToDAE3Q2VJDAR+fNU22iapyBV+luZct0YwWehTi lLfHUYnMTNtIEVtQuzO+iXcIMXvuzZQTjod0gx/8b86BeqcRh021OQQOcihqxVj4KEM8 Fyu9BOsm7NEOvLdF0F7GkjaAgAB0y5rQ7NDwr70+Wl4ImgwaXie5gOROQeY3Lmeksxh4 SqoBGtLoS/KRTpotDS9XVELCRajBt0awyGhN1qvcchqDryplkjpWLfNUIkd7qKb+SAN1 lGdg== X-Gm-Message-State: AOAM530qnCc4WPDnO2/zMDfYFQJA7OSUhhODIcfrQzoNz4r6OvIHD2In Eampii/jQKOhAm47jIKvuPU= X-Google-Smtp-Source: ABdhPJyu48ABbekwvtALO2JO+gDw0IjhchbBRuiUgpHvsnkMl605uS9uQX1F3s0EVoraFKz+/aPreg== X-Received: by 2002:a17:906:d9d9:: with SMTP id qk25mr3760460ejb.448.1595497933238; Thu, 23 Jul 2020 02:52:13 -0700 (PDT) Received: from kozik-lap ([194.230.155.213]) by smtp.googlemail.com with ESMTPSA id bn7sm1713556ejb.100.2020.07.23.02.52.10 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 23 Jul 2020 02:52:12 -0700 (PDT) Date: Thu, 23 Jul 2020 11:52:09 +0200 From: Krzysztof Kozlowski To: Arnd Bergmann Subject: Re: [RFC PATCH 00/23] memory: Cleanup, improve and compile test memory drivers Message-ID: <20200723095209.GA30472@kozik-lap> References: <20200723073744.13400-1-krzk@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200723_055214_714322_D40138BD X-CRM114-Status: GOOD ( 25.66 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Cc: Florian Fainelli , "open list:TEGRA ARCHITECTURE SUPPORT" , linux-omap , Tony Lindgren , Greg Kroah-Hartman , "moderated list:ARM/Mediatek SoC..." , "linux-kernel@vger.kernel.org" , Vladimir Zapolskiy , Matthias Brugger , SoC Team , arm-soc , bcm-kernel-feedback-list , Markus Mayer , Santosh Shilimkar , Olof Johansson , Thierry Reding , Andrew Morton , Jonathan Hunter , Linus Torvalds , Linux ARM , Roger Quadros Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Jul 23, 2020 at 11:31:02AM +0200, Arnd Bergmann wrote: > On Thu, Jul 23, 2020 at 9:37 AM Krzysztof Kozlowski wrote: > > > > Dear All, > > > > The drivers/memory directory contains generic code (of_memory.c) and a > > bunch of drivers. Changes to generic code were coming usually through > > different trees with the driver code. > > > > Over last days, memory drivers grew in numbers but not necessarily in > > quality. They lacked compile testing and code cleanup. Also lacked > > maintainer. > > > > I would be happy to take care about this part. > > > > If there are no objections, the patches could go either to Linus or to > > arm-soc (most of drivers are ARM specific). > > > > Driver-specific changes in the patchset were only compile-tested. Tests > > are welcome. The generic code was tested on ARMv7 Exynos based boards > > with a exynos5422-dmc memory controller driver. > > Overall this looks great, I had a look through the patches and commented > on the few things that seemed slightly odd though harmless. > > Thanks for picking up the subsystem. How do you want to proceed > in the long run? I suppose you can send a pull request to soc@kernel.org > to be picked up for the coming merge window as the normal way, since > you are not yet listed as the maintained until the end of the series. > > Afterwards you could either send the pull requests to Linus directly, > or send them to the soc team (or to Greg) as well, the way we handle > a couple of other subsystems like drivers/reset and drivers/tee that > usually only have a handful of patches per release. Most of the drivers are for ARM architecture so arm-soc seems like the way to do it. However BT1_L2_CTL and JZ4780_NEMC are MIPS specific and maybe more would come in the future. Are you fine taking them as well? Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel