Received: by 10.213.65.68 with SMTP id h4csp2513700imn; Mon, 9 Apr 2018 04:53:28 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+yz5K/2HuO3mDyoUFdMu8AZlWHVRAXfDc4AfycNztVuGGPq4+wFsv91DS+D/F2CfnR5uEF X-Received: by 2002:a17:902:d88a:: with SMTP id b10-v6mr28750456plz.172.1523274808274; Mon, 09 Apr 2018 04:53:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523274808; cv=none; d=google.com; s=arc-20160816; b=Kzo5BXhFHxtOH2R2P04tYfoX/JTgXfH+W3vDtjOraJUiFZnRD3+DldWqLREWT0Y+dA 6u7fORNnN/22zXAYdig3InEs/F4ZLnnzZdjET3pFs/yHJOw1HjYCFOR7+6VDk1kF/nsi nOSHnid4uTaympqPdwdzCWuDEpEPjXzCOcchKPh7nOeI0iOPDLfR70Tu0PsNeJpbxMCH YUvgsky6poSqX5R0G1+Dn+GcnYFGn1yzdNjpcmv5enJLzYhayHdqsN4gnMpkjDY6g4H/ ISAiX3uNvg0iNqtSJ/K2IWKQQ3OmFLg5IZd2Z8/THNNNkkPT9QB1Ih9JAs/Y9YHSJK7w fW8g== 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:dmarc-filter:arc-authentication-results; bh=305kYlbO9TBb7Xf/Z5nCeKlH1ZRsLpPhiVnGU86J4oo=; b=BYgAWTolwcOAEhPyoxejOVEAORmKq22doFr9hje2hwwkm9mbpVFvI0s9ISwnvXzi5O 5uJPhJYjTg7lqU0bNUX8cKZ3i4oKzhSh7jCS5+qL8h5VJNenNYO1PAdxuJwB6Z5yhmd8 LQPT05uC+E/E4yaTI9nWjbyDCqAlB+b+HvfSJKAoX44YvhRCazCU1S5orQq+x13Q9Tf9 8xF3hSwA9R8yNUUCjbMnVT+hPOZXtKsuS3YNQWSWlokgSKygTPscZdl7huBihZ0YwWq/ bj+3v2Bzql95jPndLszLl/jGstwgf62DsZK+0Mv2LpMyBMah+FHFBsDmnkll2pNBJwI8 JuBw== 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 d37-v6si145827plb.566.2018.04.09.04.52.51; Mon, 09 Apr 2018 04:53:28 -0700 (PDT) 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 S1751881AbeDILqc (ORCPT + 99 others); Mon, 9 Apr 2018 07:46:32 -0400 Received: from mail.kernel.org ([198.145.29.99]:52096 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522AbeDILqb (ORCPT ); Mon, 9 Apr 2018 07:46:31 -0400 Received: from dragon (unknown [104.237.91.164]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1E88320838; Mon, 9 Apr 2018 11:46:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1E88320838 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=shawnguo@kernel.org Date: Mon, 9 Apr 2018 19:46:19 +0800 From: Shawn Guo To: Arnd Bergmann Cc: Stefan Agner , Sascha Hauer , Fabio Estevam , Russell King - ARM Linux , Linux ARM , Linux Kernel Mailing List Subject: Re: [PATCH 1/7] ARM: multi_v7_defconfig: add OCOTP driver for NXP SoCs Message-ID: <20180409114618.GB14582@dragon> References: <20180318203442.19759-1-stefan@agner.ch> <20180326073214.GB8857@dragon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 27, 2018 at 03:40:33PM +0200, Arnd Bergmann wrote: > On Mon, Mar 26, 2018 at 9:32 AM, Shawn Guo wrote: > > On Sun, Mar 18, 2018 at 09:34:36PM +0100, Stefan Agner wrote: > >> Enable on-chip OTP NVMEM support for NXP i.MX and VF610 SoCs. > >> Since OTP values might be required by drivers required during > >> boot, make sure the driver is built-in (e.g. i.MX thermal > >> driver). > >> > >> Signed-off-by: Stefan Agner > > > > Arnd, > > > > The series looks good to me. In general, I keep myself away from > > multi_v7_defconfig changes, but if you expect a pull-request from me, I > > can do that. Let me know how you want to apply the patches. > > I would generally prefer that your defconfig pull requests contain changes > to both the imx specific and the generic defconfig files. It's much easier > for me to handle any conflicts when they arise during a merge than > to pick up the individual patches. Noted, thanks for the comments, Arnd. Shawn