Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp405152pxj; Fri, 11 Jun 2021 02:02:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBXcI0Ms8gli7y8zdG3IeV+pdTn188SmZhVNYGtygLTOJbSwcAsruc+taK/cXuv59z5+vE X-Received: by 2002:a17:906:4d56:: with SMTP id b22mr2636452ejv.78.1623402136668; Fri, 11 Jun 2021 02:02:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623402136; cv=none; d=google.com; s=arc-20160816; b=rkbBjkmwHIu1Ks036mfb+3bwNx5J+BBiSgkdADhNok1kLTR1haxZ7F2ehasg0aTxBY UWYyMrcNuLUnWzCAs7wd69GCHPgy0eIpVRLBMTOyTmRc+c52/VzeVug8sEABALV/OIym gY7vuP+85/Tp3V37iM6gXWTpZquEPK4hC95MI6RYTBEXmcS9cftwUIwPSCZA9gQDgKof 2+xhGwjeSL9qutY1GjBipBQSlz1Ozgk8+wWEP6PC56cAxmEr+Qg798KZuKrBU7sUvSKW 8f7wStr/4pPLOD/pXsTttGp9b6prmnj16i3hnyF4bFxLRar2xzbLtRSqXCMMIrjS54Y2 MNgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=u9T73zr86emrJHa0d/qk2kTDaIXQgcFQ66jVsaMLyRU=; b=fI5T/qaSHotNN1TBwwY6mJvhUcQCjo0uWQwgtvH9yhwi+NtnpY+tHpXN23aDIbOj6z wvQAIkhaxvAZtCFS5gvxv7Fc9PON2zq1xh+UvqE4gtwbjQoTC4uut+JeBH4bPLJvO0XD fLcBb7X+86Kw83WJev8Upvp59o//tjhXBmv5pALqrTpbGDijrmm3EyjDrNnrfe0T1cyQ 8abZgzVi59OUkzxNk0poXZmjLl8n55ynEQabq8XslxcWutwKSs2qcwjjHjOyJZCReG/k iZqsN8nMwJWpyEF+E0SoXkgru2CU32zkZLeLPY+PsvGcaNIfLh3DqkWrmlt1mNm2YVzH rQnA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l18si4228386ejr.283.2021.06.11.02.01.23; Fri, 11 Jun 2021 02:02:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231428AbhFKJBI (ORCPT + 99 others); Fri, 11 Jun 2021 05:01:08 -0400 Received: from router.aksignal.cz ([62.44.4.214]:55906 "EHLO router.aksignal.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230385AbhFKJBI (ORCPT ); Fri, 11 Jun 2021 05:01:08 -0400 Received: from localhost (localhost [127.0.0.1]) by router.aksignal.cz (Postfix) with ESMTP id BC08E47317; Fri, 11 Jun 2021 10:59:08 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at router.aksignal.cz Received: from router.aksignal.cz ([127.0.0.1]) by localhost (router.aksignal.cz [127.0.0.1]) (amavisd-new, port 10026) with LMTP id JoxcQDnsDsKA; Fri, 11 Jun 2021 10:59:08 +0200 (CEST) Received: from [172.25.161.48] (unknown [83.240.30.185]) (Authenticated sender: jiri.prchal@aksignal.cz) by router.aksignal.cz (Postfix) with ESMTPSA id 1BD0B47316; Fri, 11 Jun 2021 10:59:07 +0200 (CEST) Subject: Re: [PATCH v9 1/5] nvmem: prepare basics for FRAM support To: Greg Kroah-Hartman Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Christian Eggers , Arnd Bergmann References: <20210611052652.7894-1-jiri.prchal@aksignal.cz> <20210611052652.7894-2-jiri.prchal@aksignal.cz> From: =?UTF-8?B?SmnFmcOtIFByY2hhbA==?= Message-ID: <3c2beca6-8ef5-834d-a37a-5aea53bc1305@aksignal.cz> Date: Fri, 11 Jun 2021 10:59:07 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11. 06. 21 10:48, Greg Kroah-Hartman wrote: > On Fri, Jun 11, 2021 at 07:26:48AM +0200, Jiri Prchal wrote: >> Added enum and string for FRAM to expose it as "fram". > > I have no idea what "FRAM" is, nor what "fram" is. > > And why do you not add the documentation update here in this same > commit? This is where you are adding it, trying to dig later in the > series to notice that you really did provide this is a pain, and is > harder to track. > > Please provide more information here in the changelog and move the > Documentation addition here into this patch. Should I also join #1 and 2 together?