From: Stephen Warren <swarren@wwwdotorg.org>
To: stefan@agner.ch, chris@printf.net, linux-mmc@vger.kernel.org
Cc: linux-tegra@vger.kernel.org, linux@arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 2/2] mmc: use SD/MMC host ID for block device name ID
Date: Tue, 01 Apr 2014 14:47:36 -0600 [thread overview]
Message-ID: <533B25E8.8040201@wwwdotorg.org> (raw)
In-Reply-To: <2f6ac51155f9d34791b274b5102d15a997ff8b99.1396384101.git.stefan@agner.ch>
On 04/01/2014 02:35 PM, stefan@agner.ch wrote:
> From: Stefan Agner <stefan@agner.ch>
>
> By using the SD/MMC host device ID as a starting point for block
> device numbering, one can reliably predict the first block device
> name (at least for the first controller).
That's not true. There's no guarantee that a device name/ID gets
released as soon as the SD card is removed; something might still have
it mounted for example.
The correct solution here is to use filesystem or partition UUIDs to
identify the device/partition, not to attempt to assign static device IDs.
next prev parent reply other threads:[~2014-04-01 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 20:35 [RFC 0/2] fixed order for mmc devices/mmc block devices stefan-XLVq0VzYD2Y
2014-04-01 20:35 ` stefan
[not found] ` <cover.1396384101.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-04-01 20:35 ` [RFC 1/2] mmc: read mmc alias from device tree stefan-XLVq0VzYD2Y
2014-04-01 20:35 ` stefan
[not found] ` <5570bdf5ebb3aaae5a376634ecfbac9c2fd7b9f4.1396384101.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-08-06 19:43 ` Doug Anderson
2014-08-06 19:43 ` Doug Anderson
2015-03-13 20:08 ` Doug Anderson
2015-03-13 20:08 ` Doug Anderson
2014-04-01 20:35 ` [RFC 2/2] mmc: use SD/MMC host ID for block device name ID stefan
2014-04-01 20:47 ` Stephen Warren [this message]
[not found] ` <533B25E8.8040201-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-01 21:46 ` Stefan Agner
2014-04-01 21:46 ` Stefan Agner
[not found] ` <2f6ac51155f9d34791b274b5102d15a997ff8b99.1396384101.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-08-06 19:50 ` Doug Anderson
2014-08-06 19:50 ` Doug Anderson
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=533B25E8.8040201@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=chris@printf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=stefan@agner.ch \
/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.