linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 2/2] ARM hibernation / suspend-to-disk
Date: Wed, 16 Apr 2014 11:12:43 +0100	[thread overview]
Message-ID: <20140416101243.GA6952@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1394016605-24120-3-git-send-email-sebastian.capella@linaro.org>

On Wed, Mar 05, 2014 at 02:50:05AM -0800, Sebastian Capella wrote:
> diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
> index 8756e4b..d32adbb 100644
> --- a/arch/arm/include/asm/memory.h
> +++ b/arch/arm/include/asm/memory.h
> @@ -291,6 +291,7 @@ static inline void *phys_to_virt(phys_addr_t x)
>   */
>  #define __pa(x)			__virt_to_phys((unsigned long)(x))
>  #define __va(x)			((void *)__phys_to_virt((phys_addr_t)(x)))
> +#define __pa_symbol(x)		__pa((unsigned long)(x))
>  #define pfn_to_kaddr(pfn)	__va((pfn) << PAGE_SHIFT)

I don't see the appropriate version on the mailing list, so I'll comment
here instead.  In 8011/1, you added here:

+#define virt_to_pfn(kaddr)      (__pa(kaddr) >> PAGE_SHIFT)

which conflicts with my solution (which fixes some rather horrid assembly
code).  You can find my change as e26a9e00afc4 (ARM: Better virt_to_page()
handling).  I can drop this from your patch, but it would be a good idea
if you could re-validate against v3.15-rc1.

Thanks.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  parent reply	other threads:[~2014-04-16 10:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 10:50 [PATCH v7 0/2] hibernation support on ARM Sebastian Capella
2014-03-05 10:50 ` [PATCH v7 1/2] ARM: avoid tracers in soft_restart Sebastian Capella
2014-03-06 23:45   ` Sebastian Capella
2014-03-19 23:26     ` Sebastian Capella
2014-03-05 10:50 ` [PATCH v7 2/2] ARM hibernation / suspend-to-disk Sebastian Capella
2014-03-07  4:21   ` Sebastian Capella
2014-03-07  4:42   ` Stephen Boyd
2014-03-10 18:32     ` Sebastian Capella
2014-03-16  9:46       ` Russell King - ARM Linux
2014-03-17 22:07         ` Sebastian Capella
2014-03-16  7:09   ` Ezequiel Garcia
2014-03-17 19:10     ` Sebastian Capella
2014-03-17 20:44       ` Ezequiel Garcia
2014-03-17 22:39         ` Sebastian Capella
2014-03-19 15:44           ` Ezequiel Garcia
2014-03-19 20:47             ` Sebastian Capella
2014-03-19 21:06               ` Sebastian Capella
2014-03-24 18:06                 ` Sebastian Capella
2014-03-25 18:38                 ` Alexander Holler
2014-03-25 18:48                   ` Sebastian Capella
2014-03-25 23:36                   ` Alexander Holler
2014-03-26  0:00                     ` Alexander Holler
2014-03-20  3:02             ` TonyHo
2014-03-20 17:26               ` Sebastian Capella
2014-04-16 10:12   ` Russell King - ARM Linux [this message]
2014-04-16 16:42     ` Sebastian Capella
2014-04-17 20:38       ` Sebastian Capella
2014-04-23  0:38         ` Sebastian Capella
2014-04-23 16:39           ` Sebastian Capella
2014-05-07 15:37             ` Pavel Machek
2014-05-07 22:20               ` Sebastian Capella

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=20140416101243.GA6952@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).