From: Daniel Golle <daniel@makrotopia.org>
To: Jens Axboe <axboe@kernel.dk>,
Daniel Golle <daniel@makrotopia.org>,
Christian Marangi <ansuelsmth@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Douglas Anderson <dianders@google.com>,
Christian Brauner <brauner@kernel.org>,
Riyan Dhiman <riyandhiman14@gmail.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Li Lingfeng <lilingfeng3@huawei.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] block: partitions: of: assign Device Tree node to partition
Date: Tue, 4 Mar 2025 17:06:17 +0000 [thread overview]
Message-ID: <c0b234511303c2efbbff336ed4d5bb993b54f16b.1741107851.git.daniel@makrotopia.org> (raw)
In-Reply-To: <8cfbf225bcda906df0c89dd18ba07ecfa17123c2.1741107851.git.daniel@makrotopia.org>
Assign partition of_node so other drivers are able to identify a
partition by its Device Tree node.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
---
block/partitions/of.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/partitions/of.c b/block/partitions/of.c
index 4e760fdffb3fe..8b82f9f396866 100644
--- a/block/partitions/of.c
+++ b/block/partitions/of.c
@@ -48,7 +48,7 @@ static void add_of_partition(struct parsed_partitions *state, int slot,
u64 offset = of_read_number(reg, a_cells) / SECTOR_SIZE;
u64 size = of_read_number(reg + a_cells, s_cells) / SECTOR_SIZE;
- put_partition(state, slot, offset, size);
+ of_put_partition(state, slot, offset, size, np);
if (of_property_read_bool(np, "read-only"))
state->parts[slot].flags |= ADDPART_FLAG_READONLY;
--
2.48.1
next prev parent reply other threads:[~2025-03-04 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 17:06 [PATCH 1/2] block: allow setting partition of_node Daniel Golle
2025-03-04 17:06 ` Daniel Golle [this message]
2025-04-01 1:40 ` [PATCH 2/2] block: partitions: of: assign Device Tree node to partition Christian Marangi
2025-04-01 1:39 ` [PATCH 1/2] block: allow setting partition of_node Christian Marangi
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=c0b234511303c2efbbff336ed4d5bb993b54f16b.1741107851.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=ansuelsmth@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dianders@google.com \
--cc=koct9i@gmail.com \
--cc=lilingfeng3@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riyandhiman14@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®