From: Tabi Timur-B04825 <B04825@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] powerpc/85xx: standardize display of address map size (32-bit vs. 36-bit)
Date: Fri, 2 Sep 2011 11:36:55 +0000 [thread overview]
Message-ID: <4E60BFD6.5020304@freescale.com> (raw)
In-Reply-To: <6A841E78-5D44-4190-9899-1976234EF955@freescale.com>
Kumar Gala wrote:
> 1. We reduce the amount printed in the "default" case
> 2. First choice should always be to have a command the print status info
> 3. Allow a board port to makes its own decision if it wants to do something like enable CONFIG_PCI_SCAN_SHOW
>
> Any concerns w/that proposal?
Are you talking about my patch, or about CONFIG_PCI_SCAN_SHOW?
The reason I like my patch as-is is because it completely eliminates the
board from the decision. It's only one line, and it's CONSISTENT. That's
the key part. We have not been consistent about this, and it seems silly
for each board to implement the same feature.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-09-02 11:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 22:15 [U-Boot] [PATCH 1/2] powerpc/85xx: CONFIG_ENABLE_36BIT_PHYS does not depend on CONFIG_PHYS_64BIT Timur Tabi
2011-08-31 22:15 ` [U-Boot] [PATCH 2/2] powerpc/85xx: standardize display of address map size (32-bit vs. 36-bit) Timur Tabi
2011-09-01 14:07 ` Kumar Gala
2011-09-01 14:13 ` Timur Tabi
2011-09-01 14:22 ` Wolfgang Denk
2011-09-01 14:54 ` Timur Tabi
2011-09-01 21:59 ` Wolfgang Denk
2011-09-01 22:09 ` Timur Tabi
2011-09-05 14:11 ` Wolfgang Denk
2011-09-02 3:38 ` Kumar Gala
2011-09-02 11:36 ` Tabi Timur-B04825 [this message]
2011-09-02 13:12 ` Kumar Gala
2011-09-02 13:41 ` Timur Tabi
2011-09-02 18:24 ` Kumar Gala
2011-09-02 18:25 ` Timur Tabi
2011-09-02 22:10 ` Wolfgang Denk
2011-09-05 14:15 ` Wolfgang Denk
2011-09-05 14:14 ` Wolfgang Denk
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=4E60BFD6.5020304@freescale.com \
--to=b04825@freescale.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.