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=-1.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=ham 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 58556C43381 for ; Fri, 15 Feb 2019 15:09:10 +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 272F721A4C for ; Fri, 15 Feb 2019 15:09:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="OsxwfNzg" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 272F721A4C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-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=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=0vSWno/6RW28816hKsxY4GpAXdPJ/9pkcEe3Y6G1y2o=; b=OsxwfNzgIOmhf1 IiiN2XeoijtIbD+j43CZIx4x9MtkB8mZviQORTbwyxkbsxxGaC65oa6j0HHTjF1+LUjo861rgqDAg As2UlQ+tb3bTANo45jGYvDRpLtyWzXkdNBtiJKZ+com3V7gLkkWtOQlbyfe3RtGWs4BMlPgegFXVF qsFl0Apc3Ci0ZzB5tU3krful7tUJ6FJ4xT9+rnUmOnUnbNNaXiQ71yMyAxENAYGkoRccaUJx+t9bx wjOUKV8lSH4XC3apc3n7kG8VKabUrj9/9tVdLVEM14+V64HpAKyq/7pAKs2usJqPj4UbJ8gYG2TES mmKHhPhDaW5KseLS5ZSQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1guf6s-0007Uc-Qo; Fri, 15 Feb 2019 15:09:02 +0000 Received: from mail-qk1-f194.google.com ([209.85.222.194]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1guf6p-0007U4-Jq for linux-arm-kernel@lists.infradead.org; Fri, 15 Feb 2019 15:09:00 +0000 Received: by mail-qk1-f194.google.com with SMTP id x9so5881679qkf.0 for ; Fri, 15 Feb 2019 07:08:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4PVPCwG/YUQsu+Zl50QOu9m4GMe9Tfn2CemQvueGzrI=; b=IUr1FxkZ1M1RZMtVr+3Im6+8azj64yPtgO1i9Q1Sa1scwF6qXTYZEgseadpqvYkQG7 t/FU6+mE/qoz1kCO6gK4yOAmc2Supddr+MfFdo1RGWzluxcMnALoca+xj00/psFHXzqw Xyzh+48oCh5BjWcARRL94JhqVBn+WSe5A7qk0OfI+C8EcOBgo0pVBVccMJdFd17Irr1b 1Y8QgRn4TEwcpLRHyDakqdX3IoZhe26zg6nUMdqzYivzOIuPjxG5oqZg2dn9tSG3wIug 9nNmCAuBopDivEyqGggmqT1LJIQvzcQlkSa35k10+BxwyCm3fwDKb2tO4me9BvOUwROs blfw== X-Gm-Message-State: AHQUAubBMqhpzTrluz9TberHf6HDQvtirLoCgsy532QAl4VNyQlMtL+I 70gAG6o1eGdyw1HNzG7+1bh5EiZPlXUiBQr6Ppk= X-Google-Smtp-Source: AHgI3IYajWSPyeiK0n5k1fgzC0w4+efuBqp1htbrazIsE3NyBf7mfCC0lY5Vju2QB4FgDOtB7PZjkhgm77LFTc1v1yU= X-Received: by 2002:a37:bdc6:: with SMTP id n189mr7194447qkf.330.1550243337464; Fri, 15 Feb 2019 07:08:57 -0800 (PST) MIME-Version: 1.0 References: <20190212112126.572-1-shawnguo@kernel.org> <20190212112126.572-3-shawnguo@kernel.org> In-Reply-To: <20190212112126.572-3-shawnguo@kernel.org> From: Arnd Bergmann Date: Fri, 15 Feb 2019 16:08:41 +0100 Message-ID: Subject: Re: [GIT PULL 3/7] i.MX DT bindings update for 5.1 To: Shawn Guo X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190215_070859_649539_67A5E851 X-CRM114-Status: GOOD ( 11.02 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux ARM , arm-soc , Fabio Estevam , linux-imx@nxp.com, Sascha Hauer Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Feb 12, 2019 at 12:21 PM Shawn Guo wrote: > > Hi Arnd, Olof, > > In the past, I was simply using imx/dt branch to collect i.MX platform > related DT bindings changes, together with arm32 dts ones. Now with the > move to json-schema, we are using a single fsl.yaml file to accommodate > both arm32 and arm64 platform bindings, while we have separate branches > for dts changes - imx/dt and imx/dt64. To avoid conflicts, I chose to > create a new branch imx/bindings for i.MX platform bindings change for > this cycle. That's why we get this pull request, which you will pull > into arm-soc next/dt branch, I guess. > > For future cycles, I would like to hear your thoughts on if we can use > a single branch for both arm32 and arm64 dts changes, so that the > bindings changes can go in there too. Thanks. I'd say you could combine them if you have only a couple of changesets in total, but given the current size of the branches, I prefer having three or even more separate branches for the DT changes. Arnd _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel