From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964880AbbBDKNf (ORCPT ); Wed, 4 Feb 2015 05:13:35 -0500 Received: from cpsmtpb-ews03.kpnxchange.com ([213.75.39.6]:63206 "EHLO cpsmtpb-ews03.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753818AbbBDKNc (ORCPT ); Wed, 4 Feb 2015 05:13:32 -0500 Message-ID: <1423044809.23894.65.camel@x220> Subject: watchdog: SOC_MT7621? From: Paul Bolle To: Wim Van Sebroeck , Ralf Baechle Cc: Valentin Rothberg , Guenter Roeck , linux-watchdog@vger.kernel.org, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org Date: Wed, 04 Feb 2015 11:13:29 +0100 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Feb 2015 10:13:30.0061 (UTC) FILETIME=[39468FD0:01D04063] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org John Crispin's commit 576c618cf659 ("watchdog: add MT7621 watchdog support") was included in today's linux-next (ie, next 20150204). I noticed because a script I use to check linux-next spotted a problem with it. That commit adds an (optional) dependency on the Kconfig symbol SOC_MT7621. But there's no symbol SOC_MT7621 in linux-next yet. (Note that there currently are two checks for CONFIG_SOC_MT7621 in arch/mips/ralink/early_printk.c. I mentioned these checks in https://lkml.org/lkml/2014/10/27/218 and in https://lkml.org/lkml/2015/1/12/302 . John never replied to these messages. Since I haven't received replies on other, more serious issues in over three months I assume John has disappeared.) Is SOC_MT7621 still being worked on? Paul Bolle