From: peter.ujfalusi@ti•com (Peter Ujfalusi)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: Fix double definition of virt_to_pfn()
Date: Wed, 23 Apr 2014 13:40:15 +0300 [thread overview]
Message-ID: <5357988F.2050306@ti.com> (raw)
In-Reply-To: <20140423093700.GF24070@n2100.arm.linux.org.uk>
On 04/23/2014 12:37 PM, Russell King - ARM Linux wrote:
> On Wed, Apr 23, 2014 at 10:35:47AM +0300, Peter Ujfalusi wrote:
>> One definition of virt_to_pfn() was outside of the #if #elif #else section
>> causing constant redefinition of the macro.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti•com>
>> ---
>> Hi,
>>
>> the redefinition actually coming from different source. It is caused by the
>> leftover definition of virt_to_pfn() which would redefine the virt_to_pfn()
>> all the time.
>>
>> The redefinition still exist in next-20140423.
>
> Please see the thread "Re: [PATCH v7 2/2] ARM hibernation / suspend-to-disk"
> this month. The fixed up commit will be pushed out shortly.
Thanks, I found the thread.
--
P?ter
next prev parent reply other threads:[~2014-04-23 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 15:28 __pv_phys_offset, inline assembly functions, and such like Russell King - ARM Linux
2014-03-28 15:29 ` [PATCH] ARM: Better virt_to_page() handling Russell King
2014-03-28 19:52 ` Nicolas Pitre
2014-03-28 20:05 ` Russell King - ARM Linux
2014-03-29 2:51 ` Nicolas Pitre
2014-04-22 19:55 ` Ezequiel Garcia
2014-04-23 7:35 ` [PATCH] ARM: Fix double definition of virt_to_pfn() Peter Ujfalusi
2014-04-23 9:37 ` Russell King - ARM Linux
2014-04-23 10:40 ` Peter Ujfalusi [this message]
2014-03-28 16:44 ` __pv_phys_offset, inline assembly functions, and such like Arnd Bergmann
2014-03-28 16:56 ` Russell King - ARM Linux
2014-03-28 17:39 ` Arnd Bergmann
2014-04-04 22:32 ` [PATCH] ARM: Better virt_to_page() handling Russell King
2014-04-04 22:44 ` Russell King - ARM Linux
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=5357988F.2050306@ti.com \
--to=peter.ujfalusi@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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