From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Anatolij Gustschin <agust@denx.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: fix PHYS_64BIT selection for P1022DS
Date: Thu, 13 Oct 2011 10:35:04 -0500 [thread overview]
Message-ID: <4E970528.8080908@freescale.com> (raw)
In-Reply-To: <6F5815DD-DBF0-4155-94CE-FEDC2C9802E1@kernel.crashing.org>
Kumar Gala wrote:
>> > Why did you apply this patch? Both Scott and I rejected it.
> Because its fixing a real issue. If we want to remove PHYS_64BIT support or make it optional for the board feel free to send another patch.
Ok, so if someone posts a patch that works but does things the wrong way, and
that patch gets rejected during reviews, but the submitter doesn't post a
follow-up patch that does things the right way, you're going to apply the first
patch anyway?
What about the BSP team's contention that enabling 64-bit support in the kernel
can drop performance by up to 25% in some situations? We talked about that on
an internal mailing list several months ago.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-10-13 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 19:32 [PATCH] powerpc/85xx: fix PHYS_64BIT selection for P1022DS Anatolij Gustschin
2011-09-25 17:06 ` Tabi Timur-B04825
2011-09-26 22:12 ` Kumar Gala
2011-09-26 22:14 ` Timur Tabi
2011-09-26 22:24 ` Scott Wood
2011-10-12 4:53 ` Kumar Gala
2011-10-13 14:14 ` Tabi Timur-B04825
2011-10-13 15:31 ` Kumar Gala
2011-10-13 15:35 ` Timur Tabi [this message]
2011-10-13 15:41 ` Kumar Gala
2011-10-13 15:45 ` Timur Tabi
2011-10-13 15:52 ` Anatolij Gustschin
2011-10-13 15:50 ` Anatolij Gustschin
2011-10-13 15:59 ` Timur Tabi
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=4E970528.8080908@freescale.com \
--to=timur@freescale.com \
--cc=agust@denx.de \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).