From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
Cc: "richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>,
"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
Bernhard Frauendienst <kernel@nospam.obeliks.de>
Subject: Re: [PATCH v12 3/3] mtd: Add driver for concatenating devices
Date: Tue, 27 May 2025 10:21:26 +0200 [thread overview]
Message-ID: <87iklmv4zd.fsf@bootlin.com> (raw)
In-Reply-To: <IA0PR12MB76994AAD2E2D48932C2141C9DC65A@IA0PR12MB7699.namprd12.prod.outlook.com> (Amit Kumar Mahapatra's message of "Mon, 26 May 2025 15:01:47 +0000")
> In this approach, late_initcall() has been removed. Instead, we explicitly
> call the API at [1] to create the concat device, as by this stage all
> partitions have been parsed, individual MTD devices registered, and the
> necessary information for creating the concat device has been
> gathered.
I believe I made comments about the new approach but please resend if
you think I'm wrong, I will have a second look.
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
Cc: "richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>,
"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
Bernhard Frauendienst <kernel@nospam.obeliks.de>
Subject: Re: [PATCH v12 3/3] mtd: Add driver for concatenating devices
Date: Tue, 27 May 2025 10:21:26 +0200 [thread overview]
Message-ID: <87iklmv4zd.fsf@bootlin.com> (raw)
In-Reply-To: <IA0PR12MB76994AAD2E2D48932C2141C9DC65A@IA0PR12MB7699.namprd12.prod.outlook.com> (Amit Kumar Mahapatra's message of "Mon, 26 May 2025 15:01:47 +0000")
> In this approach, late_initcall() has been removed. Instead, we explicitly
> call the API at [1] to create the concat device, as by this stage all
> partitions have been parsed, individual MTD devices registered, and the
> necessary information for creating the concat device has been
> gathered.
I believe I made comments about the new approach but please resend if
you think I'm wrong, I will have a second look.
Miquèl
next prev parent reply other threads:[~2025-05-27 8:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 13:37 [PATCH v12 0/3] mtd: Add support for stacked memories Amit Kumar Mahapatra
2025-02-05 13:37 ` Amit Kumar Mahapatra
2025-02-05 13:37 ` [PATCH v12 1/3] dt-bindings: mtd: Describe MTD partitions concatenation Amit Kumar Mahapatra
2025-02-05 13:37 ` Amit Kumar Mahapatra
2025-02-11 21:29 ` Rob Herring
2025-02-11 21:29 ` Rob Herring
2025-02-12 8:25 ` Miquel Raynal
2025-02-12 8:25 ` Miquel Raynal
2025-02-12 16:06 ` Rob Herring
2025-02-12 16:06 ` Rob Herring
2025-02-12 16:18 ` Miquel Raynal
2025-02-12 16:18 ` Miquel Raynal
2025-02-18 21:39 ` Rob Herring
2025-02-18 21:39 ` Rob Herring
2025-02-19 8:36 ` Miquel Raynal
2025-02-19 8:36 ` Miquel Raynal
2025-02-05 13:37 ` [PATCH v12 2/3] mtd: Move struct mtd_concat definition to header file Amit Kumar Mahapatra
2025-02-05 13:37 ` Amit Kumar Mahapatra
2025-02-05 13:37 ` [PATCH v12 3/3] mtd: Add driver for concatenating devices Amit Kumar Mahapatra
2025-02-05 13:37 ` Amit Kumar Mahapatra
2025-02-05 16:23 ` Markus Elfring
2025-02-05 16:23 ` Markus Elfring
2025-03-18 15:53 ` Miquel Raynal
2025-03-18 15:53 ` Miquel Raynal
2025-03-19 6:17 ` Mahapatra, Amit Kumar
2025-03-19 6:17 ` Mahapatra, Amit Kumar
2025-03-19 8:21 ` Miquel Raynal
2025-03-19 8:21 ` Miquel Raynal
2025-04-30 14:18 ` Mahapatra, Amit Kumar
2025-04-30 14:18 ` Mahapatra, Amit Kumar
2025-05-12 10:01 ` Miquel Raynal
2025-05-12 10:01 ` Miquel Raynal
2025-05-13 14:45 ` Mahapatra, Amit Kumar
2025-05-13 14:45 ` Mahapatra, Amit Kumar
2025-05-16 14:06 ` Miquel Raynal
2025-05-16 14:06 ` Miquel Raynal
2025-05-21 6:13 ` Mahapatra, Amit Kumar
2025-05-21 6:13 ` Mahapatra, Amit Kumar
2025-05-26 8:10 ` Miquel Raynal
2025-05-26 8:10 ` Miquel Raynal
2025-05-26 14:27 ` Mahapatra, Amit Kumar
2025-05-26 14:27 ` Mahapatra, Amit Kumar
2025-05-26 14:39 ` Miquel Raynal
2025-05-26 14:39 ` Miquel Raynal
2025-05-26 15:01 ` Mahapatra, Amit Kumar
2025-05-26 15:01 ` Mahapatra, Amit Kumar
2025-05-27 8:21 ` Miquel Raynal [this message]
2025-05-27 8:21 ` Miquel Raynal
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=87iklmv4zd.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=amitrkcian2002@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=kernel@nospam.obeliks.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/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.