From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/3] mci: mci-core: set the DEVFS_IS_MCI_DEV flag
Date: Thu, 6 May 2021 13:22:18 +0200 [thread overview]
Message-ID: <20210506112219.27114-2-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20210506112219.27114-1-m.felsch@pengutronix.de>
Set the new introduced flag to be able to check if the cdev is an
mmc/mci device.
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
drivers/mci/mci-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mci/mci-core.c b/drivers/mci/mci-core.c
index 017f25d35f..c0fbcb385f 100644
--- a/drivers/mci/mci-core.c
+++ b/drivers/mci/mci-core.c
@@ -420,6 +420,7 @@ static void mci_part_add(struct mci *mci, uint64_t size,
part->size = size;
part->blk.cdev.name = name;
part->blk.cdev.partname = partname;
+ part->blk.cdev.flags |= DEVFS_IS_MCI_DEV;
part->blk.blockbits = SECTOR_SHIFT;
part->blk.num_blocks = mci_calc_blk_cnt(size, part->blk.blockbits);
part->area_type = area_type;
--
2.29.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-05-06 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 11:22 [PATCH 1/3] driver: add flag to check if cdev is an mci device Marco Felsch
2021-05-06 11:22 ` Marco Felsch [this message]
2021-05-06 12:06 ` [PATCH 2/3] mci: mci-core: set the DEVFS_IS_MCI_DEV flag Ahmad Fatoum
2021-05-06 13:07 ` Marco Felsch
2021-05-06 13:10 ` Ahmad Fatoum
2021-05-06 11:22 ` [PATCH 3/3] fs: add linux_rootarg 'root=mmcblkXpN' support Marco Felsch
2021-05-06 12:19 ` Ahmad Fatoum
2021-05-06 13:30 ` Marco Felsch
2021-05-06 11:59 ` [PATCH 1/3] driver: add flag to check if cdev is an mci device Ahmad Fatoum
2021-05-06 13:08 ` Marco Felsch
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=20210506112219.27114-2-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox