[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1416825092.10073.6.camel@x220>
Date: Mon, 24 Nov 2014 11:31:32 +0100
From: Paul Bolle <pebolle@...cali.nl>
To: Ralf Baechle <ralf@...ux-mips.org>
Cc: Valentin Rothberg <valentinrothberg@...il.com>,
linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org
Subject: MIPS: 64BIT_PHYS_ADDR
Ralf,
Your commit 5bd35e65f101 ("MIPS: Replace MIPS-specific 64BIT_PHYS_ADDR
with generic PHYS_ADDR_T_64BIT") is included in today's linux-next (ie,
next-20141124). That commit does what it promises to do. There are a few
references to 64BIT_PHYS_ADDR in linux-next:
$ git grep -n 64BIT_PHYS_ADDR
arch/mips/include/asm/pgtable-32.h:225:#endif /* defined(CONFIG_64BIT_PHYS_ADDR) && defined(CONFIG_CPU_MIPS32) */
drivers/dma/txx9dmac.c:79:#if defined(CONFIG_32BIT) && !defined(CONFIG_64BIT_PHYS_ADDR)
drivers/dma/txx9dmac.h:70:#if defined(CONFIG_32BIT) && !defined(CONFIG_64BIT_PHYS_ADDR)
drivers/dma/txx9dmac.h:204:#if defined(CONFIG_32BIT) && !defined(CONFIG_64BIT_PHYS_ADDR)
drivers/pcmcia/Kconfig:150: select 64BIT_PHYS_ADDR
drivers/pcmcia/Kconfig:161: select 64BIT_PHYS_ADDR
I assume that patches to replace these references too are queued
somewhere. Is that correct?
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists