linux-kernel - Re: [PATCH 11/12] USB: ehci-omap: Try to get PHY even if not in PHY mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 14 Mar 2013 11:08:50 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Felipe Balbi <balbi@...com>
cc:	Roger Quadros <rogerq@...com>, <gregkh@...uxfoundation.org>,
	<b-cousson@...com>, <mark.rutland@....com>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>,
	<linux-omap@...r.kernel.org>, <devicetree-discuss@...ts.ozlabs.org>
Subject: Re: [PATCH 11/12] USB: ehci-omap: Try to get PHY even if not in PHY
 mode

On Thu, 14 Mar 2013, Felipe Balbi wrote:

> > >  		if (IS_ERR(phy) || !phy) {
> > > +			/* Don't bail out if PHY is not absolutely necessary */
> > > +			if (pdata->port_mode[i] != OMAP_EHCI_PORT_MODE_PHY)
> > > +				continue;
> > > +
> > >  			ret = IS_ERR(phy) ? PTR_ERR(phy) : -ENODEV;
> > >  			dev_err(dev, "Can't get PHY device for port %d: %d\n",
> > >  					i, ret);
> > 
> > Felipe, this is a strange interface.  Why do we sometimes get an 
> > error-pointer and sometimes get just NULL?  Why not always an 
> > error-pointer?
> 
> looks like we get NULL when PHY layer is disabled. Sounds like an
> oversight to me. Do you want to send a patch, or do I cook one and put
> yourself as Reported-by ?

You're more familiar with that code.  "Reported-by" is good enough for 
me.  :-)

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/