Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754256AbdCFVFB (ORCPT ); Mon, 6 Mar 2017 16:05:01 -0500 Received: from mail.free-electrons.com ([62.4.15.54]:39900 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754123AbdCFVEw (ORCPT ); Mon, 6 Mar 2017 16:04:52 -0500 Date: Mon, 6 Mar 2017 22:02:38 +0100 From: Boris Brezillon To: Richard Weinberger , Srinivas Kandagatla Cc: Alban , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-mtd@lists.infradead.org, Cyrille Pitchen , Marek Vasut , Brian Norris , David Woodhouse , Mark Rutland , Rob Herring , Maxime Ripard , Moritz Fischer Subject: Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API Message-ID: <20170306220238.6cc3a897@bbrezillon> In-Reply-To: References: <1488484223-844-1-git-send-email-albeu@free.fr> <1488484223-844-3-git-send-email-albeu@free.fr> <20170302221803.223ff23b@bbrezillon> <20170303133629.3aac2945@tock> <20170303143658.5d89a329@bbrezillon> <20170303145726.16cd67fd@tock> <20170303151107.36754d19@bbrezillon> <54c76650-b61f-8a4c-70c7-febe76e16d3b@nod.at> <20170306182147.65d59d33@avionic-0020> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1132 Lines: 28 On Mon, 6 Mar 2017 20:03:28 +0100 Richard Weinberger wrote: > Am 06.03.2017 um 18:21 schrieb Alban: > > On Fri, 3 Mar 2017 23:21:29 +0100 > > Richard Weinberger wrote: > > > >> Am 03.03.2017 um 15:11 schrieb Boris Brezillon: > >>>> And add a list of successfully added notifiers, along with their > >>>> data pointer, to the MTD device. That's simple and would also remove > >>>> the need for notifier to have a private list of their instances as I > >>>> had to do here. > >>> > >>> And then you're abusing the notifier concept. As said earlier, a > >>> notifier is not necessarily using the device, and thus, don't > >>> necessarily need private data. > >>> It's not only about what is the simplest solution for your use case, > >>> but also what other users want/need. > >> > >> Yes, please don't use the mtd_notifier. > >> I strongly vote to embed the nvmem pointer into struct mtd_info. > > > > Ok, I'll do that. However it mean it will have to stays in > > drivers/mtd as it then become part of the MTD core. > > Brian, are you fine with this? Same question to Srinivas.