Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1746796pxb; Mon, 8 Mar 2021 05:32:44 -0800 (PST) X-Google-Smtp-Source: ABdhPJxUS/4qRov+1xN8mRMnkfdEAnBw+KltKNmZ++TBy4c0peT7Y6apnRjdfrib6YuncWXwrz0n X-Received: by 2002:aa7:ce1a:: with SMTP id d26mr22146638edv.206.1615210363849; Mon, 08 Mar 2021 05:32:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615210363; cv=none; d=google.com; s=arc-20160816; b=b2AJ+SzS931rZk0Wq3n5KqyB9pzg4De0Wg7UKOV7b5lOAglLcPt2VJGRVpxbVms3BY n1/4UewjbjiadMIR9diJDqZkF9c+YIe7LVECRz6RT9VSd7RE2Cqjv8ZxCh2fxJaIB8Uz Jt54FHew2mAZdG604gA2RDvQrHrq9Mfu4KeKUvzhUL1lbxJc+pcahwb9aBKoTemA1edI Ym77mtk5aVYjkIUx+GDVZXiHGgMLsFodgv2zCNO1C9L3z0b6RWgBYCSOmPCrtBZL4sKY 2GMeic7oIVEMSOPj9gYBuTWmFmjSqhfQr+zBYJDt05QxHGDRnIqpATMkrtiatFyUj64G liUA== 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:dkim-signature; bh=bH8SgOAbKuUs4jdIWtf1T+ZPNzyaRHJ+Vj2NV4QS1yE=; b=zgoLXB+ETMr4pMHVHvfcCdDONi9od/Hd1UZAU+MTDTsM2yWPZxHt9JVf6UR+ynEJuW dioO1oiN/43kD3a8sKkjWlDMQ8x4kK8vizN1yW5n3fK3x6fRIVa0WCo8f2b0uuxprqvD +RlWx1qAseWAsG1DeHgdcaVKLSu0Sa8RwyKWsVUf+Jm9MUGjiLQBCs1WsDA/5ab687Pc ol6YJo7OfGvckrAqd7sbu0xZS/52eTtSepPqSsIn40x2wPN6574w9QoywP4PuMIWITWt UvOiZn+TYJIOkFR412HMSRyZO1cjtTYzsH3yCPKdrgL0Tecn5YaZl7Q4Bzr17qdVfE1M IGxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=SIZd0Iss; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ju22si5098905ejc.514.2021.03.08.05.32.21; Mon, 08 Mar 2021 05:32:43 -0800 (PST) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=SIZd0Iss; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229468AbhCHN3E (ORCPT + 99 others); Mon, 8 Mar 2021 08:29:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43816 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229690AbhCHN3C (ORCPT ); Mon, 8 Mar 2021 08:29:02 -0500 Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B8B1C06174A; Mon, 8 Mar 2021 05:29:02 -0800 (PST) Received: by mail-lj1-x230.google.com with SMTP id c19so7738290ljn.12; Mon, 08 Mar 2021 05:29:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=bH8SgOAbKuUs4jdIWtf1T+ZPNzyaRHJ+Vj2NV4QS1yE=; b=SIZd0IssvVu6rbJjVXw5WIFXllzIe5pTt4e3qzSIb+igzodeKSvYtlC5u7t5Lx/Zlu itvaOx1Jqh62hPA8IhRGP7YjL56pmJP/fPMIC83rjzzrBgI7kq3FoVXe828ZlvnGgVAa haVoVGySaDBc/UWdSqDH7u775B9Z5zG/wKg+Nuz1mAol7UtILOf7ya5Ej32I4ZzW7vT1 IkPjxr2H8Nwgj2Y34DkPvCjLsk+VjqQd1P3kZykPVnRHLmxUjZUmCyfPLVFIo20A9QjV /ExFyTijZ3e7qqPa8+lab7Zgghb62lYzjkZxP7jPIOq+OM8QrsNd5XFh/EBbHyvefFkO UfKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bH8SgOAbKuUs4jdIWtf1T+ZPNzyaRHJ+Vj2NV4QS1yE=; b=VbeX9E6cfwHZX5j3saoK/Sa061js8y8FnprKTyDi1BVl7WV6/741PyQYbpTtdMeM0D qciP8bC9JO5GMR78Pu5GbSfEe/22gDNLUp2OkR8UZyu+Cc8GzSodASld4q3cDiDOIRXF M+/200zaIrEjuSGXm+KavklhHLkQJR/JP4perIzZ8CCalSIe27It9W4ezJwE8NMAJgP3 bAuIHhYYq78UCEUUgmD9TBTnEV2879GAvTrkAvBX0lJ24f2jEeXhwNu3hIs76qNdmJpX PlG6xS8xSHMX2U/FMmZEXWTArUm15UUllXcsmeyQMNTgUvaP938poIfEvi9PLqEEZpY1 WJQg== X-Gm-Message-State: AOAM533kQCrFw/LrQuj9gYBEif9iRJCo1EEW392vYTByhZMMgV63Ys1m 5XJbQbqtRQek+2CyXRkV0Mk= X-Received: by 2002:a05:651c:2005:: with SMTP id s5mr11473619ljo.491.1615210140467; Mon, 08 Mar 2021 05:29:00 -0800 (PST) Received: from localhost.localdomain (ip-194-187-74-233.konfederacka.maverick.com.pl. [194.187.74.233]) by smtp.googlemail.com with ESMTPSA id t7sm1394599lfd.180.2021.03.08.05.28.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Mar 2021 05:28:59 -0800 (PST) Subject: Re: [PATCH v2 3/3] dt-bindings: mtd: Document use of nvmem-partitions compatible To: Ansuel Smith Cc: Richard Weinberger , devicetree@vger.kernel.org, Vignesh Raghavendra , Boris Brezillon , linux-kernel@vger.kernel.org, Rob Herring , linux-mtd@lists.infradead.org, Miquel Raynal References: <20210216212638.28382-1-ansuelsmth@gmail.com> <20210216212638.28382-4-ansuelsmth@gmail.com> From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Message-ID: <9ca010ed-930a-2387-2be1-18e3b558d83d@gmail.com> Date: Mon, 8 Mar 2021 14:28:58 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07.03.2021 18:04, Ansuel Smith wrote: > On Mon, Mar 08, 2021 at 10:48:32AM +0100, Rafał Miłecki wrote: >> On 16.02.2021 22:26, Ansuel Smith wrote: >>> Document nvmem-partitions compatible used to treat mtd partitions as a >>> nvmem provider. >> >> I'm just wondering if "nvmem-partitions" is accurate enough. Partitions >> bit sounds a bit ambiguous in the mtd context. >> >> What do you think about "mtd-nvmem-cells" or just "nvmem-cells"? > > I read somewhere that mtd is not so standard so "nvmem-cells" should be the > right compatible. > To sum up, with v2 I should change the compatible name and just push the > 2 and 3 patch. (waiting your fix to be accepted) Correct? Yes, I believe so