public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: yingjie_bai@126•com, Scott Wood <oss@buserror•net>,
	Kumar Gala <galak@kernel•crashing.org>
Cc: Jason Yan <yanaijie@huawei•com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux•ibm.com>,
	linux-kernel@vger•kernel.org, Nicholas Piggin <npiggin@gmail•com>,
	Paul Mackerras <paulus@samba•org>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse•de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
	Bai Yingjie <byj.tea@gmail•com>,
	Thomas Gleixner <tglx@linutronix•de>,
	linuxppc-dev@lists•ozlabs.org,
	Allison Randal <allison@lohutok•net>
Subject: Re: [PATCH v3 1/2] powerpc32/booke: consistently return phys_addr_t in __pa()
Date: Wed, 29 Jan 2020 16:17:31 +1100 (AEDT)	[thread overview]
Message-ID: <486sDq372qz9sRh@ozlabs.org> (raw)
In-Reply-To: <20200106042957.26494-1-yingjie_bai@126.com>

On Mon, 2020-01-06 at 04:29:53 UTC, yingjie_bai@126•com wrote:
> From: Bai Yingjie <byj.tea@gmail•com>
> 
> When CONFIG_RELOCATABLE=y is set, VIRT_PHYS_OFFSET is a 64bit variable,
> thus __pa() returns as 64bit value.
> But when CONFIG_RELOCATABLE=n, __pa() returns 32bit value.
> 
> When CONFIG_PHYS_64BIT is set, __pa() should consistently return as
> 64bit value irrelevant to CONFIG_RELOCATABLE.
> So we'd make __pa() consistently return phys_addr_t, which is 64bit
> when CONFIG_PHYS_64BIT is set.
> 
> Signed-off-by: Bai Yingjie <byj.tea@gmail•com>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/6ad4afc97bc6c5cca9786030492ddfab871ce79e

cheers

      parent reply	other threads:[~2020-01-29  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  4:29 [PATCH v3 1/2] powerpc32/booke: consistently return phys_addr_t in __pa() yingjie_bai
2020-01-06  4:29 ` [PATCH v3 2/2] powerpc/mpc85xx: also write addr_h to spin table for 64bit boot entry yingjie_bai
2020-01-06 18:05   ` Scott Wood
2020-01-29  5:17 ` Michael Ellerman [this message]

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=486sDq372qz9sRh@ozlabs.org \
    --to=patch-notifications@ellerman$(echo .)id.au \
    --cc=allison@lohutok$(echo .)net \
    --cc=aneesh.kumar@linux$(echo .)ibm.com \
    --cc=byj.tea@gmail$(echo .)com \
    --cc=galak@kernel$(echo .)crashing.org \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=npiggin@gmail$(echo .)com \
    --cc=nsaenzjulienne@suse$(echo .)de \
    --cc=oss@buserror$(echo .)net \
    --cc=paulus@samba$(echo .)org \
    --cc=tglx@linutronix$(echo .)de \
    --cc=yanaijie@huawei$(echo .)com \
    --cc=yingjie_bai@126$(echo .)com \
    /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