From: Dr. Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 0/2] disk: efi: allow gap before partition entries
Date: Tue, 21 Feb 2017 19:21:42 +0100 [thread overview]
Message-ID: <F3AAFC8F-1DFA-4B84-9FA5-1FAD7DA79E09@theobroma-systems.com> (raw)
In-Reply-To: <20170221174544.5ipptktenlfkei5v@lukather>
> On 21 Feb 2017, at 18:45, Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>
> However, I'm a bit skeptical on the /config node. First, this node
> doesn't exist at all, and needs to be documented and acked by the DT
> maintainers. And why would one need to change that per device?
What?s the consensus on this: remove the /config-node dependency
(or split off into a separate patch), make the CONFIG-option a first
class citizen and add to Kconfig? and reroll as v2?
?Phil.
next prev parent reply other threads:[~2017-02-21 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 17:31 [U-Boot] [PATCH v1 0/2] disk: efi: allow gap before partition entries Philipp Tomsich
2017-02-17 17:31 ` [U-Boot] [PATCH v1 1/2] part_efi: support padding between the GPT header and " Philipp Tomsich
2017-02-22 3:59 ` Simon Glass
2017-02-17 17:31 ` [U-Boot] [PATCH v1 2/2] sunxi-common: add EFI_PARTITION_ENTRIES_OFF, CONFIG_RANDOM_UUID and CONFIG_CMD_GPT Philipp Tomsich
2017-02-21 17:45 ` [U-Boot] [PATCH v1 0/2] disk: efi: allow gap before partition entries Maxime Ripard
2017-02-21 18:10 ` Dr. Philipp Tomsich
2017-02-21 18:21 ` Dr. Philipp Tomsich [this message]
2017-02-22 17:38 ` Maxime Ripard
2017-02-22 6:11 ` Rask Ingemann Lambertsen
2017-02-22 10:08 ` Dr. Philipp Tomsich
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=F3AAFC8F-1DFA-4B84-9FA5-1FAD7DA79E09@theobroma-systems.com \
--to=philipp.tomsich@theobroma-systems.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.