All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs/fat: add a parameter: allow_whole_dev to fat_register_device()
Date: Thu, 12 Jun 2014 22:07:18 -0600	[thread overview]
Message-ID: <539A78F6.9070702@nvidia.com> (raw)
In-Reply-To: <539A70FF.4080003@atmel.com>

On 06/12/2014 09:33 PM, Josh Wu wrote:
> Dear Wolfgang
> 
> On 6/12/2014 4:52 PM, Wolfgang Denk wrote:
>> Dear Josh Wu,
>>
>> In message <53995100.9080307@atmel.com> you wrote:
>>> In U-Boot when we access a partition of a device, we use 'ifname
>>> dev:part' format.
>>> For instance: 'mmc 0:1' means the MMC card's #1 partition of the
>>> device #0.
>> Don;t we also support plain "ifname dev", i. e. without partition
>> specification?
> 
> The problem is we only support "ifname dev" on command line mode or the
> filesystem call which calls get_device_and_partition().

Why not just replace the calls to fat_register_device() with calls to
get_device_and_partition() (perhaps some wrapper is needed to make the
APIs match). That way, someone (U-Boot config file author I suppose) can
always specify exactly what they want, without needing any
non-deterministic fallbacks.

  reply	other threads:[~2014-06-13  4:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  5:57 [U-Boot] [PATCH] fs/fat: add a parameter: allow_whole_dev to fat_register_device() Josh Wu
2014-06-12  6:26 ` Wolfgang Denk
2014-06-12  7:04   ` Josh Wu
2014-06-12  8:52     ` Wolfgang Denk
2014-06-13  3:33       ` Josh Wu
2014-06-13  4:07         ` Stephen Warren [this message]
2014-06-13  4:54           ` Josh Wu
2014-06-14 20:07             ` Tom Rini
2014-06-13  4:38         ` Wolfgang Denk
2014-06-13 13:40         ` Tom Rini

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=539A78F6.9070702@nvidia.com \
    --to=swarren@nvidia.com \
    --cc=u-boot@lists.denx.de \
    /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.