From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: fix build failure in code for mach-bcmring/dma.c
Date: Sun, 22 Jan 2012 18:32:37 -0500 [thread overview]
Message-ID: <4F1C9C95.2060600@windriver.com> (raw)
In-Reply-To: <20120122211723.GB12326@n2100.arm.linux.org.uk>
On 12-01-22 04:17 PM, Russell King - ARM Linux wrote:
> On Sun, Jan 22, 2012 at 04:09:39PM -0500, Paul Gortmaker wrote:
>> Upstream commit 99d1717dd7fecf2b10195b0d864323b952b4eba0
>>
>> "ARM: Add init_consistent_dma_size()"
>>
>> essentially did this:
>>
>> -#define CONSISTENT_BASE (CONSISTENT_END - CONSISTENT_DMA_SIZE)
>> +unsigned long consistent_base = CONSISTENT_END - DEFAULT_CONSISTENT_DMA_SIZE;
>>
>> but the bcmring code was still using the old CONSISTENT_BASE
>> macro. Update it to now use the dynamic variable that reflects
>> the ability to resize early at boot. To do so involves putting
>> the variable alongside of init_consistent_dma_size in dma-mapping.h
>
> Oh god, what are the bcmring people doing with this variable?
[snip original BCM code]
> So really, this code is broken. It needs to be fixed, rather than fixing
> the core ARM code to allow this brokenness to persist.
I can't argue with that; if the build regression happens
to shine a light on bigger issues, then the appropriate people
are on the CC (I hope). It is beyond me to figure out what
the original code's intent was - but at least they will now
know when it broke and why...
Thanks,
Paul.
next prev parent reply other threads:[~2012-01-22 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 21:09 [PATCH] arm: fix build failure in code for mach-bcmring/dma.c Paul Gortmaker
2012-01-22 21:17 ` Russell King - ARM Linux
2012-01-22 23:32 ` Paul Gortmaker [this message]
2012-01-23 18:53 ` Jiandong Zheng
2012-01-23 20:18 ` Russell King - ARM Linux
2012-01-23 20:37 ` Jiandong Zheng
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=4F1C9C95.2060600@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-arm-kernel@lists.infradead.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