linux-kernel - Re: [PATCH 1/3] ARM: zynq: remove TTC early mapping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHTX3dK2AEGh72XMuPSyBCV1sdM6jDvdiyPdh5VGXhTnwOqWTA@mail.gmail.com>
Date:	Tue, 20 Nov 2012 13:41:16 +0100
From:	Michal Simek <monstr@...str.eu>
To:	Josh Cartwright <josh.cartwright@...com>
Cc:	arm@...nel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] ARM: zynq: remove TTC early mapping

2012/11/19 Josh Cartwright <josh.cartwright@...com>:
> Now that the TTC driver has proper support for DT bindings, it is not
> necessary for the registers to be mapped early.  They will be mapped
> during clock initialization using of_iomap().  Remove the early mapping.
>
> In addition, remove the extraneous zynq_soc.h include from the timer
> driver.
>
> Signed-off-by: Josh Cartwright <josh.cartwright@...com>
> ---
>  arch/arm/mach-zynq/common.c                | 5 -----
>  arch/arm/mach-zynq/include/mach/zynq_soc.h | 6 +-----
>  arch/arm/mach-zynq/timer.c                 | 1 -
>  3 files changed, 1 insertion(+), 11 deletions(-)

Tested-by: Michal Simek <michal.simek@...inx.com>

Applied to xilinx arm-next branch.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
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/