Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp980767imu; Mon, 5 Nov 2018 11:48:03 -0800 (PST) X-Google-Smtp-Source: AJdET5cxvnxRSOAJ0Kf1VkVAWzzrY2ZN+w4W6sEHITgVljiUj95irYZcANqeKbJM1ebqk30+i+cr X-Received: by 2002:a62:cdc1:: with SMTP id o184-v6mr9042386pfg.181.1541447283256; Mon, 05 Nov 2018 11:48:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541447283; cv=none; d=google.com; s=arc-20160816; b=FypWtpYquTzFYHJr6aut8es/J1dYTIlFmiliZGSGu+3J242UAFOZFhDJbggzyid43y CLZ6e5Goh9+79HWDu8CRHaU3Zzd8l8cIpnblYc2g+hkoiUzXaYN11GNXbAm8Ao27hhzg RgsZHyqZqc0fQOEQS+qHgYfQQKE6Q2U72n7WJeXWgJ9mUfwMiZF0iykZtk4DJcBUTzw9 9WWbIWWOKP3AcGxLkoVuRXsooa55jDIalxX5xWIyM2NvzApujyJ+cBFXtBrbP/tjLnol fXOSxdM1GM/02JhwultC+ELJrtULV+T6zPD6e9cWXQiyG1KE6kXnQjDDI6h0SC4T2ZBY yRRg== 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=iOlwTVFEq0X/yPnc8ly8BJ/asD3tAMiE3agBBFaIYHs=; b=tV4B1TpUcgU9yu0NOUIM1ivrT2GRHoSVUWYXyng2Tx+AgF3Sxh1AMykiGiDxYKR9vv 8bo++0EBfolEFWUYgY0LZS70Dz8mpCVeOQBXq8igZUP3f6NCWddys85F2p+6KRS59bqu 6N2gF053POWqQu7E6DKzFCpR2+eBuDSMRWBBZFezcuiM04lUoR5sOHbiT1InH+bJfHt/ PJbiIN+FdPpHeA7sozLIuFAoM4ms+J68hKzFleyRTIXX1HpoYJ+I9klcF4dhpD1gYm/v zkIZLrbPLOK0eYwBr6cbLONhiowgkGnGBlVomAKNJRu72NNT5KMJ2CIsbJABOGCasUsR iAUw== 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 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o31si13137664pgb.273.2018.11.05.11.47.47; Mon, 05 Nov 2018 11:48:03 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726608AbeKFFIj (ORCPT + 99 others); Tue, 6 Nov 2018 00:08:39 -0500 Received: from mail.skyhub.de ([5.9.137.197]:39190 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725878AbeKFFIj (ORCPT ); Tue, 6 Nov 2018 00:08:39 -0500 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de Received: from mail.skyhub.de ([127.0.0.1]) by localhost (blast.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lWL8hVrHuikP; Mon, 5 Nov 2018 20:47:22 +0100 (CET) Received: from zn.tnic (p200300EC2BCD5300329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2bcd:5300:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 62A961EC01F6; Mon, 5 Nov 2018 20:47:22 +0100 (CET) Date: Mon, 5 Nov 2018 20:47:21 +0100 From: Borislav Petkov To: Olof Johansson Cc: Michal Simek , Arnd Bergmann , manish.narani@xilinx.com, Rob Herring , Mark Rutland , Mauro Carvalho Chehab , Amit Kucheria , Sudeep Holla , Li Yang , DTML , Linux Kernel Mailing List , Linux ARM Mailing List , linux-edac@vger.kernel.org Subject: Re: [PATCH v10 5/6] arm64: zynqmp: Add DDRC node Message-ID: <20181105194721.GB26868@zn.tnic> References: <1540447621-22870-1-git-send-email-manish.narani@xilinx.com> <1540447621-22870-6-git-send-email-manish.narani@xilinx.com> <20181105125644.GA7937@zn.tnic> <41c5ca53-ed4b-38d0-c612-e1229004293e@xilinx.com> <20181105132007.GB7937@zn.tnic> <20181105134218.GD7937@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Olof, On Mon, Nov 05, 2018 at 06:51:26AM -0800, Olof Johansson wrote: > In general, for new functionality where needing both the driver change > and a DT change to enable it (or a driver change and a config change > to enable it), we have been merging the changes separately between > driver trees and arm-soc. I.e. things will be in place, but not > enabled, until both sides land. Main reason for doing so is to cut > down on arbitrary dependencies between the trees, since there can > sometimes end up being a lot of them. Well, makes sense too and it is the least problematic approach. :-) > Since DT should strive for being backwards compatible (i.e, a driver > change shouldn't require a DT change for the kernel to not regress > functionally), this has been working pretty well. Ok. > However, if there's some other reason to share a base between the two > trees, we can do that. For most cases we've found that it's not needed > though. So let us know what you prefer here. No, I just wanted to make sure drivers can still function when they go to linux-next. But I certainly can get on board with keeping drivers and DT changes separate as it requires no sync and the short period of time when they don't load in linux-next, is perfectly ok. So can I assume you guys are going to pick up: https://lkml.kernel.org/r/1538667328-9465-7-git-send-email-manish.narani@xilinx.com https://lkml.kernel.org/r/1540447621-22870-6-git-send-email-manish.narani@xilinx.com ? I can then pick up the rest. And I'll be ignoring DT stuff sent to me from now on and concentrate on the EDAC drivers, assuming former will go through your tree. Sounds good? Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.