Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756977AbbEVKS7 (ORCPT ); Fri, 22 May 2015 06:18:59 -0400 Received: from mga01.intel.com ([192.55.52.88]:38552 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756429AbbEVKS4 (ORCPT ); Fri, 22 May 2015 06:18:56 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,474,1427785200"; d="scan'208";a="733642597" Date: Fri, 22 May 2015 13:16:38 +0300 From: Heikki Krogerus To: Sasha Levin Cc: "Lu, Baolu" , David Cohen , gregkh@linuxfoundation.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, balbi@ti.com Subject: Re: [PATCH] usb: ulpi: don't register drivers if bus doesn't exist Message-ID: <20150522101637.GB26704@kuha.fi.intel.com> References: <1432150406-20550-1-git-send-email-sasha.levin@oracle.com> <20150520212235.GA20943@psi-dev26.jf.intel.com> <555D7DB4.6030606@linux.intel.com> <20150521072133.GA16847@kuha.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150521072133.GA16847@kuha.fi.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 864 Lines: 28 > > >>diff --git a/drivers/usb/common/ulpi.c b/drivers/usb/common/ulpi.c > > >>index 0e6f968..0b0a5e7 100644 > > >>--- a/drivers/usb/common/ulpi.c > > >>+++ b/drivers/usb/common/ulpi.c > > >>@@ -132,6 +132,10 @@ int ulpi_register_driver(struct ulpi_driver *drv) > > >> if (!drv->probe) > > >> return -EINVAL; > > >>+ /* Was the bus registered successfully? */ > > >>+ if (!ulpi_bus.p) > > >>+ return -ENODEV; > > I think we need to warn in this case. How about: > > if (unlikely(WARN_ON(!ulpi_bus.p))) > return -ENODEV; I think we should also return -EAGAIN here. Thanks, -- heikki -- 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/