From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Bolle Subject: PM / OPP: ARCH_HAS_OPP Date: Mon, 28 Jul 2014 14:47:12 +0200 Message-ID: <1406551632.5397.17.camel@x220> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from cpsmtpb-ews05.kpnxchange.com ([213.75.39.8]:52651 "EHLO cpsmtpb-ews05.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752328AbaG1MrO (ORCPT ); Mon, 28 Jul 2014 08:47:14 -0400 Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: Mark Brown Cc: Viresh Kumar , Nishanth Menon , Rob Herring , Shawn Guo , Simon Horman , "Rafael J. Wysocki" , linux-pm@vger.kernel.org Mark, Your commit 78c5e0bb145d ("PM / OPP: Remove ARCH_HAS_OPP") landed in today's linux-next (ie, next-20140728). It removes the Kconfig symbol ARCH_HAS_OPP and ten select statements for that symbol. After that commit there are still nine select statements for that symbol left in linux-next. (These select statements are now actually NOPs.) The peculiar thing is that these nine statements are all found in Kconfig files also touched by that commit. Anyhow, are patches to remove these pointless select statements queued somewhere? Paul Bolle