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]
Message-Id: <201209061303.02454.arnd@arndb.de>
Date:	Thu, 6 Sep 2012 13:03:02 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	"ABRAHAM, KISHON VIJAY" <kishon@...com>
Cc:	Greg KH <gregkh@...uxfoundation.org>, Felipe Balbi <balbi@...com>,
	grant.likely@...retlab.ca, rob.herring@...xeda.com,
	rob@...dley.net, linux@....linux.org.uk, b-cousson@...com,
	rnayak@...com, tony@...mide.com,
	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-omap@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH v7 1/7] drivers: usb: phy: add a new driver for omap usb2 phy

On Thursday 06 September 2012, ABRAHAM, KISHON VIJAY wrote:
> > diff --git a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt b/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > index d2fe064..bb0c7f4 100644
> > --- a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > +++ b/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
> > @@ -8,3 +8,6 @@ properties:
> >
> >  Sub-nodes:
> >  All the devices connected to ocp2scp are described using sub-node to ocp2scp
> > +- usb2phy :
> > +   The binding details of usb2phy can be found in:
> > +   Documentation/devicetree/bindings/usb/omap-usb.txt
> 
> The above two lines should be added in omap-ocp2scp.txt (this file was
> added as part of omap: add ocp2scp as a bus driver and is in
> linux-next). However this file is still not in Felipe's xceiv branch.
> So I'm not sure how I can get this patch merged in Felipe's tree
> without conflict.
> 

There are three possible ways to do that:

* Not add that text. Is is actually required? The ocp2scp bus driver 
doesn't actually care what is connected to it, does it?

* Ask Felipe to merge the drivers/ocp2scp branch from arm-soc into
his branch, then apply your patch on top. The branch is scheduled
for merging in 3.7 and is stable, so there is no harm merging it
into his tree, as long as Olof and I are aware of this.

* Split out this change and apply the patch to add this documentation
change on top of the drivers/ocp2scp branch in the arm-soc tree.
There is no strict dependency between this change and the others
you want to merge, so it does not matter which tree it is merged through.

	Arnd
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ