From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/4] of: partition: add no-fixup device tree property
Date: Fri, 14 Dec 2018 16:31:50 +0100 [thread overview]
Message-ID: <f4e71979-864a-f090-9080-24939d859385@pengutronix.de> (raw)
In-Reply-To: <20181210083937.7edjbvfih57shwrz@pengutronix.de>
Hello,
On 10/12/18 09:39, Sascha Hauer wrote:
>
> Still why do we need a device tree property when all we have to do is to
> not call of_partitions_register_fixup() for the boot partitions?
I figured current users might want to keep the current behavior, but ok,
I will send another patch that skips fixup for the eMMC boot partitions.
You can still merge the first two patches in this patchset however, they
are applicable regardless.
Cheers
Ahmad
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-12-14 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 6:34 [PATCH 1/4] driver: left shift 1U instead of 1 in bitmask for consistency Ahmad Fatoum
2018-12-07 6:34 ` [PATCH 2/4] of: partition: use NULL instead of never-read argument Ahmad Fatoum
2018-12-07 6:34 ` [PATCH 3/4] of: partitions: make macro name more generic Ahmad Fatoum
2018-12-07 6:34 ` [PATCH 4/4] of: partition: add no-fixup device tree property Ahmad Fatoum
2018-12-07 7:43 ` Sascha Hauer
2018-12-07 8:38 ` Ahmad Fatoum
2018-12-10 8:39 ` Sascha Hauer
2018-12-14 15:31 ` Ahmad Fatoum [this message]
2019-05-23 15:43 ` Ahmad Fatoum
2019-05-24 6:31 ` Sascha Hauer
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=f4e71979-864a-f090-9080-24939d859385@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox