From: Dinh Nguyen <dinguyen@kernel.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2 2/2] arm: socfpga: clean up common config options
Date: Thu, 21 Apr 2016 08:59:35 -0500 [thread overview]
Message-ID: <5718DCC7.5090402@kernel.org> (raw)
In-Reply-To: <20160420142133.GB10360@bill-the-cat>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/20/2016 09:21 AM, Tom Rini wrote:
> On Tue, Apr 19, 2016 at 08:41:52PM -0500, Dinh Nguyen wrote:
>
>> Move common config options like these to socfpga_*_defconfig:
>>
>> CONFIG_CMD_ASKENV CONFIG_CMD_BOOTZ CONFIG_CMD_CACHE
>> CONFIG_CMD_DHCP CONFIG_CMD_EXT4 CONFIG_CMD_EXT4_WRITE
>> CONFIG_CMD_FAT CONFIG_CMD_FS_GENERIC CONFIG_CMD_GREPENV
>> CONFIG_CMD_MEMTEST CONFIG_CMD_MII CONFIG_CMD_MMC CONFIG_CMD_PING
>> CONFIG_CMD_SF CONFIG_CMD_SPI CONFIG_CMD_TIME
>>
>> to avoid defining them in individual SoCFPGA config files.
>
> So this is the tricky part, yes. You need to be able to use
> moveconfig.py to update _everyone_ and this easily conflicts (so
> don't do it right now, I have some stuff to push out that would
> cause it to conflict). I think I'll see if I can do this part,
> globally instead after applying your 1/2. Thanks!
>
Ok, let me resend 1/2 because I noticed that it had a duplicate defconfi
g.
Thanks,
Dinh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJXGNzHAAoJEBmUBAuBoyj08IYP/2K3kfb+cPIfMIEFkb5JugIb
ivUgPb72YB6DqJQVYdPolgYzm7WhMpul9cS7oT9gGBicnQ125RaWmjM5y80zBVqL
99+4o1gxqd62RYutGtptUFsh2muBi8xkGHtFSfBtqiOW9jDWthZ0+igrOo/IvrXB
Gh5hYAyxvyJbVOvBg1yUIZ8sCsiFo22rkTDMjUppjaLqGkX2gQJZOtOr5iIqI/K0
s4mfQNvgz8qcZ86worz3YAp/zpSC5pCIds/lh8osRPHnSW54iBPyW9+MXWYjLjj3
1A9iZFgDVRe0gZ3tjToa+9CMw4Rnm0ysL02FBX8EbNmBSHgX723Tz3Wi2AUwii3G
CArsZhJLUNXIt/Xts2xlJAdGtX497NsnFL9gG9vCg2Ftmdf508+AxCzyoyOuWHTK
IuVabhLKCk0xJUNBqZ6LV1Y6csXFz3U0B6xLrFtOjC1ys5WAkLpzvfKo0pLbDZFW
siJ4wvmMxpJbBTMPiFQ4o0ddoDsGI0k6T0vGuTVxm4DZFeQ9cR+YJ1KTpFkxHiqt
Y4+o/wbMnFSl7XmCEW9AbsFg7l+jpIkOO+YmrKhX2Dawz/0nUupnyW6ka/PIhaIg
NDY5yzBjQz59YKzxbvmEHIr0EmSnYZPG0idvIZf+ufSP/lm1s4vTq9PgGALUleGX
rKsnrB5Az289CWrltLYO
=xfzS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-04-21 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 1:41 [U-Boot] [PATCH 1/2] cmd: Kconfig: Add a Kconfig options for a few CMD Dinh Nguyen
2016-04-20 1:41 ` [U-Boot] [PATCHv2 2/2] arm: socfpga: clean up common config options Dinh Nguyen
2016-04-20 12:15 ` Stefan Roese
2016-04-20 14:21 ` Tom Rini
2016-04-21 13:59 ` Dinh Nguyen [this message]
2016-04-20 14:41 ` [U-Boot] [PATCH 1/2] cmd: Kconfig: Add a Kconfig options for a few CMD Simon Glass
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=5718DCC7.5090402@kernel.org \
--to=dinguyen@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox