Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752624AbaGDHiB (ORCPT ); Fri, 4 Jul 2014 03:38:01 -0400 Received: from cpsmtpb-ews10.kpnxchange.com ([213.75.39.15]:65296 "EHLO cpsmtpb-ews10.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751149AbaGDHh7 (ORCPT ); Fri, 4 Jul 2014 03:37:59 -0400 Message-ID: <1404459477.27680.10.camel@x220> Subject: usb: gadget: net2280: CONFIG_USB_GADGET_PDEBUG_FILES? From: Paul Bolle To: Ricardo Ribalda Delgado , Felipe Balbi , Greg Kroah-Hartman Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Date: Fri, 04 Jul 2014 09:37:57 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-2.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Jul 2014 07:37:57.0902 (UTC) FILETIME=[E00FDAE0:01CF975A] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit e56e69cc0ff4 ("usb: gadget: net2280: Use pr_* function") is included in today's linux-next (ie, next-20140704). It contains this odd chunk: @@ -1566,7 +1563,7 @@ static const struct usb_gadget_ops net2280_ops = { /*-------------------------------------------------------------------------*/ -#ifdef CONFIG_USB_GADGET_DEBUG_FILES +#ifdef CONFIG_USB_GADGET_PDEBUG_FILES /* FIXME move these into procfs, and use seq_file. * Sysfs _still_ doesn't behave for arbitrarily sized files, (Commit b7ca96655ddd ("usb: gadget: Gadget directory cleanup - group UDC drivers"), also included in today's linux-next, moved that new check for CONFIG_USB_GADGET_PDEBUG_FILES to drivers/usb/gadget/udc/net2280.c.) Using CONFIG_USB_GADGET_PDEBUG_FILES appears to be just an editing mistake. Would Ricardo like to submit the trivial patch to clean it up or should I do that? Paul Bolle -- 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/