Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752840AbbF3Hqz (ORCPT ); Tue, 30 Jun 2015 03:46:55 -0400 Received: from mail-yk0-f170.google.com ([209.85.160.170]:35227 "EHLO mail-yk0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752401AbbF3Hqk (ORCPT ); Tue, 30 Jun 2015 03:46:40 -0400 MIME-Version: 1.0 In-Reply-To: <55910B3E.9070405@linaro.org> References: <1434841352-24300-1-git-send-email-paul.gortmaker@windriver.com> <55910B3E.9070405@linaro.org> Date: Tue, 30 Jun 2015 09:46:38 +0200 Message-ID: Subject: Re: [tip:timers/core] clocksource: Increase dependencies of timer-stm32 to limit build wreckage From: Maxime Coquelin To: Daniel Lezcano Cc: hpa@zytor.com, mingo@kernel.org, paul.gortmaker@windriver.com, Linus Walleij , Thomas Gleixner , "linux-kernel@vger.kernel.org" , linux-tip-commits@vger.kernel.org, Chanwoo Choi Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 33 2015-06-29 11:09 GMT+02:00 Daniel Lezcano : > On 06/22/2015 10:05 AM, Maxime Coquelin wrote: > > [ ... ] > >>> --- >>> drivers/clocksource/Kconfig | 4 ++-- >>> 1 file changed, 2 insertions(+), 2 deletions(-) >>> >> >> Thanks Paul for the patch. >> Actually, I already had sent a patch to fix this dependency issue [0]. >> I thought Daniel had pick it, but don't find it in his tree. >> My patch adds a build dependency on GENERIC_CLOCKEVENTS, which I think >> is the best way to fix the problem. > > > Yes, I have it in my tree but I was expecting some more fixes to pick up in > order to send a PR to Thomas. > > Is it possible you send your a fix on top of this patch ? So I can drop your > initial patch. > Sure. I will rebase my patch on top of Paul's one. Thanks, Maxime -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/