From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 1/3] dm: blk: add UCLASS_PARTITION
Date: Tue, 29 Jan 2019 16:37:12 +0100 [thread overview]
Message-ID: <f0b72917-7565-2a13-2950-327818c3f0ef@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.21.1901281906590.64510@maverick.koi8.net>
On 01/29/2019 04:17 AM, Sergey Kubushyn wrote:
> On Tue, 29 Jan 2019, AKASHI Takahiro wrote:
>
> My $.25 -- IMHO, block device partitions in Device Tree is _NOT_ a
> very good
> idea.
This is about device model, not device tree :). Device trees indeed
should not contain partition information. Our internal object model
however would do well if it had them.
Alex
next prev parent reply other threads:[~2019-01-29 15:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 2:59 [U-Boot] [RFC 0/3] dm, efi: integrate efi_disk into DM AKASHI Takahiro
2019-01-29 2:59 ` [U-Boot] [RFC 1/3] dm: blk: add UCLASS_PARTITION AKASHI Takahiro
2019-01-29 3:17 ` Sergey Kubushyn
2019-01-29 15:37 ` Alexander Graf [this message]
2019-01-29 17:46 ` Sergey Kubushyn
2019-01-29 18:02 ` Philipp Tomsich
2019-01-29 22:20 ` Heinrich Schuchardt
2019-01-30 5:28 ` AKASHI Takahiro
2019-01-31 1:00 ` Simon Glass
2019-01-29 2:59 ` [U-Boot] [RFC 2/3] efi_loader: associate BLK/PARTITION device to efi_disk AKASHI Takahiro
2019-01-29 22:33 ` Heinrich Schuchardt
2019-01-30 5:48 ` AKASHI Takahiro
2019-01-30 6:49 ` Heinrich Schuchardt
2019-01-30 7:26 ` AKASHI Takahiro
2019-01-31 1:22 ` Simon Glass
2019-02-01 5:54 ` AKASHI Takahiro
2019-02-02 14:15 ` Simon Glass
2019-02-06 3:15 ` AKASHI Takahiro
2019-02-06 7:54 ` AKASHI Takahiro
2019-01-29 2:59 ` [U-Boot] [RFC 3/3] drivers: align block device drivers with DM-efi integration AKASHI Takahiro
2019-01-29 16:19 ` Alexander Graf
2019-01-30 0:40 ` AKASHI Takahiro
2019-01-29 16:20 ` [U-Boot] [RFC 0/3] dm, efi: integrate efi_disk into DM Alexander Graf
2019-01-29 22:48 ` Heinrich Schuchardt
2019-01-30 5:18 ` AKASHI Takahiro
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=f0b72917-7565-2a13-2950-327818c3f0ef@suse.de \
--to=agraf@suse.de \
--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.