diff for duplicates of <20130415195030.9F7E93E0AA8@localhost> diff --git a/a/1.txt b/N1/1.txt index 88f9875..effa750 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -168,11 +168,11 @@ So I would assume that for an i2c-controlled phy, and i2c driver would bind against the device, and the probe hook would create and register a phy device. That would make the sysfs tree look something like: -/sys/devices/.../i2c@80000000/usbphy@2/phy0 +/sys/devices/.../i2c at 80000000/usbphy at 2/phy0 -where, i2c@80000000 is the i2c master, usbphy@2 is what the phy's driver +where, i2c at 80000000 is the i2c master, usbphy at 2 is what the phy's driver binds against, and phy0 is created and registered by the driver of -usbphy@2 at probe time. Correct? +usbphy at 2 at probe time. Correct? > We are currently not looking at having Ethernet use this layer because > it itself has a comprehensive PHY layer and merging it with this will diff --git a/a/content_digest b/N1/content_digest index e56e4b7..995b964 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,33 +2,10 @@ "ref\01363770725-13717-2-git-send-email-kishon@ti.com\0" "ref\020130415113416.7C3943E0AA8@localhost\0" "ref\0516BF1E2.3020104@ti.com\0" - "From\0Grant Likely <grant.likely@secretlab.ca>\0" - "Subject\0Re: [PATCH v3 1/6] drivers: phy: add generic PHY framework\0" + "From\0grant.likely@secretlab.ca (Grant Likely)\0" + "Subject\0[PATCH v3 1/6] drivers: phy: add generic PHY framework\0" "Date\0Mon, 15 Apr 2013 20:50:30 +0100\0" - "To\0Kishon Vijay Abraham I <kishon@ti.com>\0" - "Cc\0balbi@ti.com" - gregkh@linuxfoundation.org - arnd@arndb.de - akpm@linux-foundation.org - rob@landley.net - davem@davemloft.net - cesarb@cesarb.net - linux-usb@vger.kernel.org - linux-omap@vger.kernel.org - linux-kernel@vger.kernel.org - tony@atomide.com - rob.herring@calxeda.com - b-cousson@ti.com - linux@arm.linux.org.uk - eballetbo@gmail.com - javier@dowhile0.org - mchehab@redhat.com - santosh.shilimkar@ti.com - broonie@opensource.wolfsonmicro.com - swarren@nvidia.com - linux-doc@vger.kernel.org - devicetree-discuss@lists.ozlabs.org - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Mon, 15 Apr 2013 17:56:10 +0530, Kishon Vijay Abraham I <kishon@ti.com> wrote:\n" @@ -201,11 +178,11 @@ "bind against the device, and the probe hook would create and register a\n" "phy device. That would make the sysfs tree look something like:\n" "\n" - "/sys/devices/.../i2c@80000000/usbphy@2/phy0\n" + "/sys/devices/.../i2c at 80000000/usbphy at 2/phy0\n" "\n" - "where, i2c@80000000 is the i2c master, usbphy@2 is what the phy's driver\n" + "where, i2c at 80000000 is the i2c master, usbphy at 2 is what the phy's driver\n" "binds against, and phy0 is created and registered by the driver of\n" - "usbphy@2 at probe time. Correct?\n" + "usbphy at 2 at probe time. Correct?\n" "\n" "> We are currently not looking at having Ethernet use this layer because \n" "> it itself has a comprehensive PHY layer and merging it with this will \n" @@ -229,4 +206,4 @@ "\n" g. -ddc73788a5e16254a3da79214af29db7359b1929011bfaa9d8995f51c46ff1d1 +bcdfe13c768aa335d62f5b5249b4dcd75699d09b1d8e969a2eb3cfaddf5c1839
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.