All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 02/13] mtd: allow getting MTD device associated with a specific DT node
Date: Mon, 19 Sep 2022 17:49:42 +0200	[thread overview]
Message-ID: <20220919174942.729e1e4d@xps-13> (raw)
In-Reply-To: <20220919174230.59f95ca2@xps-13>


miquel.raynal@bootlin.com wrote on Mon, 19 Sep 2022 17:42:30 +0200:

> Hi Srinivas,
> 
> srinivas.kandagatla@linaro.org wrote on Fri, 16 Sep 2022 13:20:49 +0100:
> 
> > From: Rafał Miłecki <rafal@milecki.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@milecki.pl>
> > Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.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.

I see just now the "applied, thanks", I eventually remembered what all
this was about, so it's fine.

Thanks,
Miquèl

  reply	other threads:[~2022-09-19 15:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 12:20 [PATCH 00/13] nvmem: patches(set 1) for 6.1 Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 01/13] nvmem: add driver handling U-Boot environment variables Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 02/13] mtd: allow getting MTD device associated with a specific DT node Srinivas Kandagatla
2022-09-19 15:42   ` Miquel Raynal
2022-09-19 15:49     ` Miquel Raynal [this message]
2022-09-16 12:20 ` [PATCH 03/13] nvmem: core: add error handling for dev_set_name Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 04/13] dt-bindings: nvmem: mediatek: efuse: Add support for MT8188 Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 05/13] nvmem: brcm_nvram: Use kzalloc for allocating only one element Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 06/13] dt-bindings: nvmem: qfprom: add IPQ8064 and SDM630 compatibles Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 07/13] nvmem: prefix all symbols with NVMEM_ Srinivas Kandagatla
2022-09-27  9:15   ` Amit Kucheria
2022-09-16 12:20 ` [PATCH 08/13] nvmem: sort config symbols alphabetically Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 09/13] dt-bindings: nvmem: Add SoC compatible for sm6115 Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 10/13] nvmem: u-boot-env: find Device Tree nodes for NVMEM cells Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 11/13] dt-bindings: lan9662-otpc: document Lan9662 OTPC Srinivas Kandagatla
2022-09-16 12:20 ` [PATCH 12/13] nvmem: lan9662-otp: add support Srinivas Kandagatla
2022-09-16 12:21 ` [PATCH 13/13] nvmem: u-boot-env: fix crc32 casting type Srinivas Kandagatla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220919174942.729e1e4d@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=srinivas.kandagatla@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.