linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Michal Hocko <mhocko@kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] mm/memblock: replace u64 with phys_addr_t where appropriate
Date: Wed, 4 Jul 2018 16:54:49 +0900	[thread overview]
Message-ID: <20180704075449.GB458@jagdpanzerIV> (raw)
In-Reply-To: <20180704070305.GB4352@rapoport-lnx>

On (07/04/18 10:03), Mike Rapoport wrote:
>  arch/alpha/kernel/pci_iommu.c             | 20 ++++++++++----------
>  arch/arm/mm/alignment.c                   |  2 +-
>  arch/arm/nwfpe/fpmodule.c                 |  2 +-
>  arch/microblaze/mm/pgtable.c              |  2 +-
>  arch/sparc/kernel/ds.c                    |  2 +-
>  arch/um/kernel/sysrq.c                    |  2 +-
>  arch/x86/include/asm/trace/exceptions.h   |  2 +-
>  arch/x86/kernel/irq_64.c                  |  2 +-
>  arch/x86/mm/extable.c                     |  4 ++--
>  arch/x86/xen/multicalls.c                 |  2 +-

Isn't it "funny" that parisc, ia64, powerpc don't use pf/pF in arch code,
but x86, arm, etc. do use pf/pF in arch code?

Surely, I do understand why we have pf/pF in mm, drivers and all over the
place. But still, I'm surprised.

	-ss

  parent reply	other threads:[~2018-07-04  7:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 17:05 [PATCH] mm/memblock: replace u64 with phys_addr_t where appropriate Mike Rapoport
2018-07-03 17:22 ` Pavel Tatashin
2018-07-03 19:57 ` Andrew Morton
2018-07-03 20:24   ` Joe Perches
2018-07-04  7:03     ` Mike Rapoport
2018-07-04  7:23       ` Sergey Senozhatsky
2018-07-04  9:04         ` Joe Perches
2018-07-04  9:20           ` Sergey Senozhatsky
2018-07-04  9:43             ` Sergey Senozhatsky
2018-07-04 15:20               ` Mike Rapoport
2018-07-04  7:54       ` Sergey Senozhatsky [this message]
2018-07-04 15:21         ` Mike Rapoport
2018-07-04 17:22       ` Joe Perches
2018-07-05  7:12         ` Mike Rapoport
2018-07-04  7:02   ` Mike Rapoport
2018-07-04 13:05 ` Michal Hocko
2018-07-04 13:24   ` Mike Rapoport
2018-07-04 13:29     ` Michal Hocko
2018-07-04 14:04 ` Michal Hocko

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=20180704075449.GB458@jagdpanzerIV \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@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).