From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: layerscape: Enable UUID & GPT partition for NXP's ARM SoC
Date: Mon, 23 Jan 2017 09:28:20 -0500 [thread overview]
Message-ID: <20170123142820.GK10853@bill-the-cat> (raw)
In-Reply-To: <f30897c5-eb1f-b604-3ffc-d88ca3e8be15@compulab.co.il>
On Mon, Jan 23, 2017 at 11:40:22AM +0200, Igor Grinberg wrote:
> On 01/19/17 19:31, york sun wrote:
> > On 12/25/2016 10:45 PM, Prabhakar Kushwaha wrote:
> >> Enable UUID and GPT partition support for NXP's ARM based SoCs
> >> i.e. LS1012A, LS1021A, LS1043A, LS1046A and LS2080A.
> >>
> >> Also enable DOS partition for LS1012AFRDM boards.
> >>
> >> Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> >> ---
> >
> > Applied to fsl-qoriq master, awaiting upstream. Thanks.
>
> Well, of course it is your call, but that's sad.
> Why not request people to move things to Kconfig?
>
> I would suggest removing these from scripts/config_whitelist.txt...
The problem with the partition table and related options is that it ends
up being a non-trivial conversion to do and remain size neutral.
Patrick, have you had a chance to look at your patch again? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170123/d7f4d096/attachment.sig>
prev parent reply other threads:[~2017-01-23 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 6:45 [U-Boot] [PATCH] arm: layerscape: Enable UUID & GPT partition for NXP's ARM SoC Prabhakar Kushwaha
2016-12-26 7:29 ` Igor Grinberg
2017-01-04 21:41 ` york sun
2017-01-05 9:51 ` Igor Grinberg
2017-01-05 16:25 ` york sun
2017-01-05 18:08 ` Igor Grinberg
2017-01-19 17:31 ` york sun
2017-01-23 9:40 ` Igor Grinberg
2017-01-23 14:28 ` Tom Rini [this message]
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=20170123142820.GK10853@bill-the-cat \
--to=trini@konsulko.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.