From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756523AbbJHLZ1 (ORCPT ); Thu, 8 Oct 2015 07:25:27 -0400 Received: from mga14.intel.com ([192.55.52.115]:40017 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756507AbbJHLZZ (ORCPT ); Thu, 8 Oct 2015 07:25:25 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,654,1437462000"; d="scan'208";a="576530924" From: Alexander Shishkin To: Greg KH Cc: linux-kernel@vger.kernel.org, Alexander Shishkin Subject: [PATCH] stm class: Select configfs Date: Thu, 8 Oct 2015 14:25:11 +0300 Message-Id: <1444303511-11393-1-git-send-email-alexander.shishkin@linux.intel.com> X-Mailer: git-send-email 2.6.0 In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org STM policy handling is basically configfs, I honestly don't know how we ended up without a Kconfig dependency, but thanks to randconfig testing, it's now caught. Reported-by: Jim Davis Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/hwtracing/stm/Kconfig b/drivers/hwtracing/stm/Kconfig index 5a59a28cc3..83e9f591a5 100644 --- a/drivers/hwtracing/stm/Kconfig +++ b/drivers/hwtracing/stm/Kconfig @@ -1,5 +1,6 @@ config STM tristate "System Trace Module devices" + select CONFIGFS_FS help A System Trace Module (STM) is a device exporting data in System Trace Protocol (STP) format as defined by MIPI STP standards. -- 2.5.3