From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754064AbaIVQP4 (ORCPT ); Mon, 22 Sep 2014 12:15:56 -0400 Received: from relay1.mentorg.com ([192.94.38.131]:58771 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752344AbaIVQPz (ORCPT ); Mon, 22 Sep 2014 12:15:55 -0400 Message-ID: <54204B32.5000905@mentor.com> Date: Mon, 22 Sep 2014 11:15:46 -0500 From: Nathan Lynch User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Will Deacon CC: Daniel Lezcano , Catalin Marinas , Christopher Covington , Doug Anderson , Lorenzo Pieralisi , Marc Zyngier , Mark Rutland , Russell King , Sonny Rao , Stephen Boyd , Thomas Gleixner , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v2 0/3] arm_arch_timer: VDSO preparation, code consolidation References: <1411052390-27238-1-git-send-email-nathan_lynch@mentor.com> <20140922153919.GQ25809@arm.com> In-Reply-To: <20140922153919.GQ25809@arm.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/22/2014 10:39 AM, Will Deacon wrote: > On Thu, Sep 18, 2014 at 03:59:32PM +0100, Nathan Lynch wrote: >> This series contains the necessary changes to allow architected timer >> access from user-space on 32-bit ARM. This allows the VDSO to support >> high resolution timestamps for clock_gettime and gettimeofday. This >> also merges substantially similar code from arm and arm64 into the >> core arm_arch_timer driver. >> >> The functional changes are: >> - When available, CNTVCT is made readable by user space on arm, as it >> is on arm64. >> - The clocksource name becomes "arch_mem_counter" if CP15 access to >> the counter is not available. >> >> These changes have been carried as part of the ARM VDSO patch set over >> the last several months, but I am splitting them out here as I assume >> they should go through the clocksource maintainers. > > For the series: > > Acked-by: Will Deacon > > I'm not sure which tree the arch-timer stuff usually goes through, but > the arm/arm64 bits look fine so I'm happy for them to merged together. Thanks Will. MAINTAINERS does not have a specific entry for drivers/clocksource/arm_arch_timer.c, so I am working under the assumption that the series would go through Daniel or Thomas. Daniel and/or Thomas, can you take this series please?