[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023102100-tile-spinning-fa1b@gregkh>
Date: Sat, 21 Oct 2023 19:18:14 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: srinivas.kandagatla@...aro.org
Cc: linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>,
Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: [PATCH 4/6] Revert "nvmem: add new config option"
On Fri, Oct 20, 2023 at 11:55:43AM +0100, srinivas.kandagatla@...aro.org wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> This reverts commit 517f14d9cf3533d5ab4fded195ab6f80a92e378f.
>
> It seems that "no_of_node" config option was added to help mtd's case.
>
> DT nodes of MTD partitions (that are also NVMEM devices) may contain
> subnodes that SHOULD NOT be treated as NVMEM fixed cells. To prevent
> NVMEM core code from parsing them "no_of_node" was set to true and that
> made for_each_child_of_node() in NVMEM a no-op.
>
> With the introduction of "add_legacy_fixed_of_cells" config option
> things got more explicit. MTD subsystem simply tells NVMEM when to look
> for fixed cells and there is no need to hack "of_node" pointer anymore.
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
> Reviewed-by: Miquel Raynal <miquel.raynal@...tlin.com>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Why isn't this also marked for stable trees?
thanks,
greg k-h
Powered by blists - more mailing lists