Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753667AbbFARzY (ORCPT ); Mon, 1 Jun 2015 13:55:24 -0400 Received: from mail-wg0-f53.google.com ([74.125.82.53]:33294 "EHLO mail-wg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752676AbbFARzU (ORCPT ); Mon, 1 Jun 2015 13:55:20 -0400 Date: Mon, 1 Jun 2015 18:55:13 +0100 From: Lee Jones To: Valentin Rothberg Cc: Andreas Ruprecht , Paul Bolle , hengelein Stefan , wim@iguana.be, david.paris@st.com, linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org Subject: Re: watchdog: st_wdt: select on undefined MFD_ST_LPC Message-ID: <20150601175513.GG3329@x1> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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: 1135 Lines: 34 On Mon, 01 Jun 2015, Valentin Rothberg wrote: > Hi Lee, > > your commit d0c9e350b9a4 ("watchdog: st_wdt: Add new driver for ST's > LPC Watchdog") is in today's linux-next tree (i.e., next-20150601) and > adds the following lines of code to drivers/watchdog/Kconfig. > > +config ST_LPC_WATCHDOG > ... > + select MFD_ST_LPC > > The select turns out to be a NOOP since MFD_ST_LPC is not defined > Kconfig. Is it the correct option to be selected? I could not find a > similar option in the source, nor get any hints from searching the > lkml. > > I detected the issue with ./scripts/checkkconfigsymbols.py by diffing > the last and today's linux tree. You're right. This symbol is legacy. I will remove. Thanks for reporting. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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/