linux-kernel - Re: [PATCH v7 1/7] usb: move the OTG state from the USB PHY to the OTG structure

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 31 Oct 2014 14:55:35 +0100
From:	Antoine Tenart <antoine.tenart@...e-electrons.com>
To:	Felipe Balbi <balbi@...com>
Cc:	Peter Chen <peter.chen@...escale.com>,
	Aaro Koskinen <aaro.koskinen@....fi>,
	Antoine Tenart <antoine.tenart@...e-electrons.com>,
	gregkh@...uxfoundation.org, kishon@...com,
	stern@...land.harvard.edu, alexandre.belloni@...e-electrons.com,
	thomas.petazzoni@...e-electrons.com, zmxu@...vell.com,
	jszhang@...vell.com, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 1/7] usb: move the OTG state from the USB PHY to the
 OTG structure

Hi Felipe,

On Fri, Oct 31, 2014 at 08:47:51AM -0500, Felipe Balbi wrote:
> On Fri, Oct 31, 2014 at 08:33:19AM -0500, Felipe Balbi wrote:
> > > > > > > > > Before using the PHY framework instead of the USB PHY one, we need to
> > > > > > > > > move the OTG state into another place, since it won't be available when
> > > > > > > > > USB PHY isn't used. This patch moves the OTG state into the OTG
> > > > > > > > > structure, and makes all the needed modifications in the drivers
> > > > > > > > > using the OTG state.
> > > > > > > > > 
> > > > > > > > > Signed-off-by: Antoine Tenart <antoine.tenart@...e-electrons.com>
> > > > > > > > > Acked-by: Peter Chen <peter.chen@...escale.com>
> > > > > > > > 
> > > > > > > > Acked-by: Felipe Balbi <balbi@...com>
> > > > > > > 
> > > > > > > Please rebase on my testing/next and I'll take the series. When
> > > > > > > rebasing, then add Peter's Tested-by/Acked-by where they're missing.
> > > > > > 
> > > > > > I just re-sent the series, rebased on your testing/next branch.
> > > > > 
> > > > > Thanks, I put them on my testing/next and I'm running build tests.
> > > > > 
> > > > 
> > > > I see them, I will rebase your testing/next tree for coming chipidea dev, thanks.
> > > 
> > > I fixed a build breakage caused by $subject which I fixed, updated patch
> > > below: (Aaro, can I get a tested-by by any chance ?)
> > 
> > two more build regressions found (did you build test your patches ??)
> 
> and yet another one on phy-isp1301-omap.c. Seriously, if I find another
> build regression I'll drop your series from my queue and defer it to
> 3.20. This is ridiculous already.

Sorry for the inconvenience, the series modify quite a lot of files and
testing all of them is quite difficult. If you'd like I can fully test
it and send a new version early next week.

Deferring it to 3.20 will not solve the issue and will raise the same
errors as these build failures. The series has been sent for quite a
long time now, without having any comments on the latests revisions and
was therefore delayed. Each time it is delayed, it makes it more
difficult to ensure everything is working fine because of all the
modifications done in this subsystem... I tried to keep it up with all
the other patches introduced between my revisions, but this is not as
easy as it sounds.

Again, sorry for these failures, I can send to you a new version early
next week so that no other patches comes in between, breaking the
build...


Antoine

-- 
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
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/