Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4545673ybl; Mon, 26 Aug 2019 12:02:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqwKYn/yqBpvfYTGf76VoxDGNHOjgunrzV1U/zgE6LxVi0J2kP8A9Zk++B1bttceEC9opkPP X-Received: by 2002:a17:902:7610:: with SMTP id k16mr5012831pll.242.1566846140729; Mon, 26 Aug 2019 12:02:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566846140; cv=none; d=google.com; s=arc-20160816; b=NSGfX6J1A7rGI34BNMst/4hRP25oRwoel/8KMUChN1g9fY1fQWKUVpC+4XnIIHhcmw MregOcZKQzxK/lhOLPHsgYcHmx47DjBGa2X63z2wpaf5oBwkvX5mHfDeY4AEP4zSw82s +IMsNOY6aOvGAWPEphnAdZMdhpav+7jAUXdBlbHxOi24wKLLPNHPqIBSj9R3HHJ4KCaW BCxfxFBvjtgN4gPqpeeRV9V6EavL2NBJJSO4RT+u7iIDY2fdRCaJBeoIiYnDmZklFnpc o9hP9T8T6a7LP4HmkXRGUiebQEJBtcmY0+sx/Lh5mFtlUyfPjv+mDQX14IhEdf084+rc g4rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=LkBa3xlPOxOIGFlL1z8V5TVoSldQC5MdlkD84cfKRv8=; b=C+CtrkADH6r73CmkJghrGIWaRrOwPv0iYLC2aW4RB5cZpaB6bQ+8K991vR2dMcclwj LTJ/dpk3mIVE8IScSq61geZFBFNzKcKblHa5+KDErkNV6wISXbzmLqYt+DHFLjW8h4v6 OAHwdb2hgEKmVH1jcj2ZwJ9NzMpUkZLRHbEOIFRZUsRNK0iTdu7wzeKyncWUF5Sm89V1 IH4r1CS/s3O6sAeMuScD3RXZZtcohK2HHyLM76pZ5YvCM754ylrPLPMJocm0u0C2RZo+ Yp0nulTxwmnVGePkFzSdYH2/496LQB38487/Oy4lRdWFXPKO7nAAwWpm8s+FtzB2GENY XEHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tHtspKsJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h4si11043396plk.268.2019.08.26.12.02.04; Mon, 26 Aug 2019 12:02:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tHtspKsJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387760AbfHZSNy (ORCPT + 99 others); Mon, 26 Aug 2019 14:13:54 -0400 Received: from mail-ed1-f68.google.com ([209.85.208.68]:41566 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731907AbfHZSNx (ORCPT ); Mon, 26 Aug 2019 14:13:53 -0400 Received: by mail-ed1-f68.google.com with SMTP id w5so27694317edl.8; Mon, 26 Aug 2019 11:13:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LkBa3xlPOxOIGFlL1z8V5TVoSldQC5MdlkD84cfKRv8=; b=tHtspKsJDGE101W9EwqaVw0RgyBItM+nuQ0t4HmFQxw8OOnTGWImttNiNv8SFEded0 euMRRkgZfC6mLuNlT/9iBPDDCsrvMQRx6qLvSmCo3mqRpNXnzs1owfAUkCA0ufyldWzk a1vT7AJxa/lJFTDDZgGrNtxKfMEFCd0hc6Ey/0EvQKJetmZGByWPnf3nCrjkPZwtdQzJ 2u4MaQUsrRM+/yYqGgNO44TpoKI57WUyZxletgfGyw6jPTWLk4o122qcSOGoe3J0hC2j Yo/DICe8ZKzPGUT1WkkyBuDUxnExLklDPdp6YlQler4ppFFb1gkE5TChtinAvj7OsX1F T1pQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LkBa3xlPOxOIGFlL1z8V5TVoSldQC5MdlkD84cfKRv8=; b=romdlgEE06Xe3gnt0aFqWnmPYyyYDsl5S6ZzZpkA6oltODiHl9aDxgnzAdEk2MCS04 GGxfFQw/KFlOqxfRkDNPMBxyFktsiQCqzwsAQTpLF8sIuQSJJu+drOR9zbkkxQ2fntcD LSDMlncNAYB2/T2XYiUAWsA1bKVBUBK+LOPA9bhI0FENcXb1YOxkxeY04Gb578jkZL1z iGZ6AX0ODGTjiMnXNaVrY4JaXXtw5D8cJOElwBZ9cYRUhMcpUUGjre10P/vj1YNGsP0q boPna9724wpgdV5EYjjIY1q9Z2cTHfCIRm7+JQj9VEPuAaftt96zE+WERdeqDkt4Dj+H Axwg== X-Gm-Message-State: APjAAAVKmYkw1FkuxE/z3pVserg57DkCUqyYN0zQGXyq6SYJbl1eGYT1 Eddah+bH50bTTLfaEntFtRAne5PjGWTjUNR0Nt8W/qyvSI0= X-Received: by 2002:a50:9401:: with SMTP id p1mr19812028eda.189.1566843231777; Mon, 26 Aug 2019 11:13:51 -0700 (PDT) MIME-Version: 1.0 References: <20190823124553.19364-1-yuehaibing@huawei.com> <20190823140513.GB9844@piout.net> <4b608c55-2541-30cf-ad88-c19a5c0cc84f@huawei.com> <01a2b6b2-eb15-1b40-1edc-de122bbdb5a2@roeck-us.net> In-Reply-To: <01a2b6b2-eb15-1b40-1edc-de122bbdb5a2@roeck-us.net> From: Bruno Thomsen Date: Mon, 26 Aug 2019 20:13:35 +0200 Message-ID: Subject: Re: [PATCH -next] rtc: pcf2127: Fix build error without CONFIG_WATCHDOG_CORE To: Guenter Roeck Cc: Yuehaibing , Alexandre Belloni , a.zummo@towertech.it, linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Den man. 26. aug. 2019 kl. 15.20 skrev Guenter Roeck : > > On 8/26/19 1:12 AM, Yuehaibing wrote: > > > > > > On 2019/8/23 22:05, Alexandre Belloni wrote: > >> On 23/08/2019 20:45:53+0800, YueHaibing wrote: > >>> If WATCHDOG_CORE is not set, build fails: > >>> > >>> drivers/rtc/rtc-pcf2127.o: In function `pcf2127_probe.isra.6': > >>> drivers/rtc/rtc-pcf2127.c:478: undefined reference to `devm_watchdog_register_device' > >>> > >>> Add WATCHDOG_CORE Kconfig dependency to fix this. > >>> > >>> Reported-by: Hulk Robot > >>> Fixes: bbc597561ce1 ("rtc: pcf2127: add watchdog feature support") > >>> Signed-off-by: YueHaibing > >>> --- > >>> drivers/rtc/Kconfig | 2 ++ > >>> 1 file changed, 2 insertions(+) > >>> > >>> diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig > >>> index 25af63d..9dce7dc 100644 > >>> --- a/drivers/rtc/Kconfig > >>> +++ b/drivers/rtc/Kconfig > >>> @@ -886,6 +886,8 @@ config RTC_DRV_DS3232_HWMON > >>> config RTC_DRV_PCF2127 > >>> tristate "NXP PCF2127" > >>> depends on RTC_I2C_AND_SPI > >>> + depends on WATCHDOG > >> > >> Definitively not, I fixed it that way: > >> + select WATCHDOG_CORE if WATCHDOG > > > > > > No, this still fails while WATCHDOG is not set > > > > Correct, there are no dummy functions for watchdog device registration. > There would have to be conditional code in the driver if the watchdog > is supposed to be optional. Hi During review of version 1, there was a wish for the watchdog feature not to be hidden behind Kconfig option, e.g. RTC_DRV_PCF2127_WDT, as it would not result in a much bigger driver. I did not add any other selects/depends on in Kconfig as RTC_DRV_DS1374_WDT and RTC_DRV_M41T80_WDT options does not select WATCHDOG_CORE and/or WATCHDOG either. DS1374 and M41T80 does not seem to check on any other WATCHDOG defines other then their _WDT Kconfig. I can create a patch that hides the watchdog code if WATCHDOG define is not set, if that's the right way? Bruno