Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753448AbbKBJPN (ORCPT ); Mon, 2 Nov 2015 04:15:13 -0500 Received: from mail-wi0-f177.google.com ([209.85.212.177]:36313 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061AbbKBJPJ (ORCPT ); Mon, 2 Nov 2015 04:15:09 -0500 Date: Mon, 2 Nov 2015 10:15:08 +0100 From: Valentin Rothberg To: peter.chen@freescale.com Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, Andreas Ziegler Subject: Documentation: update of USB_CHIPIDEA_DEBUG Message-ID: <20151102091508.GB100007@vm-valentin> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline 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: 1430 Lines: 30 Hi Peter, your commit 2fb2884ed856 ("usb: chipidea: delete static debug support") has shown up in today's Linux next tree (i.e., next-20151102) and removes the Kconfig option USB_CHIPIDEA_DEBUG in favor of dynamic debug support. However, there are some documentary references on this option still left in the code that may need to be updated: Documentation/usb/chipidea.txt-9-If you want to check some internal variables for otg fsm, Documentation/usb/chipidea.txt:10:select CONFIG_USB_CHIPIDEA_DEBUG, there are 2 files which ^^^^^^^^^^^^^^^^^^^^^^^^^ Documentation/usb/chipidea.txt-11-can show otg fsm variables and some controller registers value: -- drivers/usb/chipidea/core.c-25- * Compile Options drivers/usb/chipidea/core.c:26: * - CONFIG_USB_CHIPIDEA_DEBUG: enable debug facilities ^^^^^^^^^^^^^^^^^^^^^^^^^ drivers/usb/chipidea/core.c-27- * - STALL_IN: non-empty bulk-in pipes cannot be halted I'm just pointing to those references, since I don't know if you want to keep them in the code or not. I found the issue and your commit with scipts/checkkconfigsymbols.py. Kind regards, Valentin -- 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/