Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932111AbcLHLFP (ORCPT ); Thu, 8 Dec 2016 06:05:15 -0500 Received: from foss.arm.com ([217.140.101.70]:58274 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752738AbcLHLFK (ORCPT ); Thu, 8 Dec 2016 06:05:10 -0500 Date: Thu, 8 Dec 2016 11:04:10 +0000 From: Mark Rutland To: Fu Wei Cc: Timur Tabi , kbuild test robot , Linaro ACPI Mailman List , Catalin Marinas , Will Deacon , Wim Van Sebroeck , Wei Huang , Tomasz Nowicki , Daniel Lezcano , ACPI Devel Maling List , Guenter Roeck , kbuild-all@01.org, "Abdulhamid, Harb" , Julien Grall , linux-watchdog@vger.kernel.org, Arnd Bergmann , Marc Zyngier , Jon Masters , Christopher Covington , Thomas Gleixner , "linux-arm-kernel@lists.infradead.org" , "Rafael J. Wysocki" , Linux Kernel Mailing List , Sudeep Holla , Len Brown , Christoffer Dall Subject: Re: [Linaro-acpi] [PATCH v17 08/15] clocksource/drivers/arm_arch_timer: move arch_timer_needs_of_probing into DT init call Message-ID: <20161208110410.GA9768@leverpostej> References: <20161125084623.22515-9-fu.wei@linaro.org> <201611252221.UyJ9iWPV%fengguang.wu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1175 Lines: 31 On Thu, Dec 08, 2016 at 11:16:21AM +0800, Fu Wei wrote: > Hi Timur, > > On 8 December 2016 at 01:25, Timur Tabi wrote: > > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote: > >> > >> a "+ int ret;" should be move from [12/15] to here, I have fix the > >> problem in my repo, it would happen in next patchset > >> > >> https://git.linaro.org/people/fu.wei/linux.git/log/?h=topic-gtdt-wakeup-timer_upstream_v18_devel > > > > Fu, please post v18 to the mailing list so that it can be picked up > > for 4.10 (if it's not too late already). Unfortunately, it's too late for v4.10. It hasn't been sat in linux-next at all, and we've seen kbuild test failures. Hopefully there's time to beat this into shape and get it into linux-next so that it's ready to queue for v4.11, though. > Great thanks for your suggestion! :-) > yes, you are right, I would love to post v18 ASAP. > > But I am still waiting for more feedback from the maintainers. Please post a version which passes inspection by the kbuild test robot. I haven't had a chance to look at this yet, and it'll be better to look at a version that actually works. Thanks, Mark.