[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220919174230.59f95ca2@xps-13>
Date: Mon, 19 Sep 2022 17:42:30 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH 02/13] mtd: allow getting MTD device associated with a
specific DT node
Hi Srinivas,
srinivas.kandagatla@...aro.org wrote on Fri, 16 Sep 2022 13:20:49 +0100:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> MTD subsystem API allows interacting with MTD devices (e.g. reading,
> writing, handling bad blocks). So far a random driver could get MTD
> device only by its name (get_mtd_device_nm()). This change allows
> getting them also by a DT node.
>
> This API is required for drivers handling DT defined MTD partitions in a
> specific way (e.g. U-Boot (sub)partition with environment variables).
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
> Acked-by: Miquel Raynal <miquel.raynal@...tlin.com>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Can you please keep me in Cc for the whole series, otherwise I only
receive a single patch among 13 and it does not make any sense.
Thanks,
Miquèl
Powered by blists - more mailing lists