On Tue, 2014-06-24 at 21:31 +0900, Taeung wrote:
> I guess that 'usb usb1: rpm_suspend...' have relevance to the core of
> this problem.
> or Is this problem about hardware ?
>
> If you tell a bit hints me , I'd appreciate it.
I doubt it. You can load usbcore with autosuspend=-1 to test.
But eve
On Tue, Jun 24, 2014 at 4:35 PM, Kamil Debski wrote:
> By reboot I guess that you mean typing "reboot" or by using SysRq magic
> and not power cycling?
>
> If so, I had experienced the same symptoms. I guess that the Ethernet
> chip is not reset properly and fails to enumerate without power cyclin
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git
tags/usb-serial-3.16-rc3
for you to fetch changes up to 6608569
At 2014-06-24 09:46:01, "Johan Hovold" wrote:
>On Tue, Jun 24, 2014 at 08:43:36PM +0800, 刘磊 wrote:
>> At 2014-06-23 10:49:14, "Johan Hovold" wrote:
>> >On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
>> >> On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
>
>> >> > i don't know why cre
Hi,
On Wed, Jun 25, 2014 at 4:04 AM, Sergei Shtylyov
wrote:
> Hello.
>
>
> On 06/10/2014 12:22 AM, Julius Werner wrote:
>
>>> diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
>>> index 9ffecd5..453d89e 100644
>>> --- a/drivers/usb/host/xhci.h
>>> +++ b/drivers/usb/host/xhci.h
>>> @
Hi,
Thanks for the suggestions Felipe.
We are not processing our packets in during giveback, but anyway I've
tried your patch and it results in a very little (~5%) increase in
transfer rate.
I think it is a latency issue, since running the application reports a
97% idle time on top.
The profili
Thank you very much !! , Vivek
On 06/25/2014 05:18 PM, Vivek Gautam wrote:
>
> Hi Taeung,
>
>
>
> Few questions here:
>
> 1) Preasently which hardware do you have ? Is it smdk5250 or
arndale5250 ?
I'm using new board which is made on 'arndale5250'.
So, the board which I
See my comments below:
> > + /* Reset the threshold limit */
> > + if(unlikely(usb_is_intel_qrk(pdev)))
>
> Please run your patch thru scripts/checkpatch.pl -- space needed after
> *if*.
OK, I will improve it in the PATCH v2.
>
> > + usb_set_qrk_bulk_thresh(pdev);
> > +
> >
See my comments below:
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, June 24, 2014 9:25 PM
> To: Chen, Alvin
> Cc: Alan Stern; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org; Ong,
> Boon Leong
> Subject: Re: [PATCH] USB: ehci-
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, June 24, 2014 9:25 PM
> To: Chen, Alvin
> Cc: Alan Stern; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org; Ong,
> Boon Leong
> Subject: Re: [PATCH] USB: ehci-pci: USB host controll
From: Chen, Alvin
> > On Tue, Jun 24, 2014 at 08:51:43AM -0700, Chen, Alvin wrote:
> > > diff --git a/drivers/usb/host/pci-quirks.c
> > > b/drivers/usb/host/pci-quirks.c index 00661d3..1ea8803 100644
> > > --- a/drivers/usb/host/pci-quirks.c
> > > +++ b/drivers/usb/host/pci-quirks.c
> > > @@ -823,6
Hi Sergei,
On Fri, May 30, 2014 at 7:42 PM, Yoshihiro Shimoda
wrote:
> From Sergei Shtylyov
>
> Add the generic PHY support, analogous to the USB PHY support. Intended it to
> be
> used with the PCI EHCI/OHCI drivers and the xHCI platform driver.
>
> Signed-off-by: Sergei Shtylyov
> Signed-of
On Sun, Jun 22, 2014 at 10:04:58AM +0100, Robert Jarzmik wrote:
> Add documentation for device-tree binding of arm PXA 27x udc (usb
> device) driver.
>
> Signed-off-by: Robert Jarzmik
> Cc: devicet...@vger.kernel.org
>
> ---
> Since V1: change OF id mrvl,pxa27x_udc -> marvell,pxa27x-udc
>
2014-06-25 6:46 GMT+02:00 Evgeny Boger:
> There might be 11 GPIOs in total.
do you mean "12 GPIOs"? You say later they are 0-based and the last one is "11"
> Last three GPIOs (offsets 8-11, 0-based) are shared with FDX, LNKA, SPD
> LEDs respectively.
so you mean the last "four"?
and you may wa
On Sun, Jun 22, 2014 at 10:04:57AM +0100, Robert Jarzmik wrote:
> Add support for device-tree device discovery. If devicetree is not
> provided, fallback to legacy platform data "discovery".
>
> Signed-off-by: Robert Jarzmik
> Cc: devicet...@vger.kernel.org
>
> ---
> Since V1: change OF id mrvl,
On Tue, Jun 24, 2014 at 03:56:51PM -0400, Greg KH wrote:
> On Tue, Jun 24, 2014 at 10:38:38PM +0300, Janne Kanniainen wrote:
> > static int gt683r_led_probe(struct hid_device *hdev,
> > const struct hid_device_id *id)
> > @@ -261,6 +272,7 @@ static int gt683r_led_probe(struct
[Adding Daniel to Cc]
At Tue, 24 Jun 2014 13:52:14 -0400 (EDT),
Alan Stern wrote:
>
> Takashi and Clemens:
>
> The snd-usb-audio driver has a race between close and disconnect. A
> patch I have been testing reliably triggers this race on my machine and
> reveals a use-after-free bug.
>
> This
A struct member variable is set to the same value more than once
This was found using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
arch/arm/mach-omap2/usb-tusb6010.c |1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-omap2/usb-tusb6010.
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With the patches for regulators' nodes merged in 3.15:
c8c253f ARM: dts: Add regulator entries to smdk5420
275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
the exynos systems turn on only minimal number of re
Facilitate getting required 3.3V and 1.0V VDD supply for
OHCI controller on Exynos.
With patches for regulators' nodes merged in 3.15:
c8c253f ARM: dts: Add regulator entries to smdk5420
275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
the exynos systems turn on only minimal number of regula
On Wed, Jun 25 2014, Robert Baldyga wrote:
> We wrap numeric values of fs_count and hs_count fields in htole32,
> because they should be in little-endian format.
>
> Signed-off-by: Robert Baldyga
Acked-by: Michal Nazarewicz
> ---
> tools/usb/ffs-aio-example/multibuff/device_app/aio_multibuff.
On Wed, Jun 25 2014, Robert Baldyga wrote:
> Since commit [ac8dde11: “Add flags to descriptors block”] functionfs
> supports a new descriptor format, so we update example application
> to make it using recomended version of descriptors.
>
> Signed-off-by: Robert Baldyga
Acked-by: Michal Nazarewi
On Wed, Jun 25 2014, Robert Baldyga wrote:
> Add missing information about license. Some people will probably want
> to reuse this code in their projects released under variety of
> licenses. For this reason this example is under Public Domain license
> to avoid GPL limitations.
I would stick to
On 06/24/2014 05:01 PM, vichy wrote:
> hi Mathias:
> 2014-06-24 16:38 GMT+08:00 Mathias Nyman :
>> On 06/23/2014 03:44 PM, David Laight wrote:
>>> From: vichy
hi all:
when i trace xhci source, I found in skip_isoc_td, there is a
possibility to increase de-queue pointer twice.
>>
On Wed, 25 Jun 2014, Takashi Iwai wrote:
> [Adding Daniel to Cc]
>
> At Tue, 24 Jun 2014 13:52:14 -0400 (EDT),
> Alan Stern wrote:
> >
> > Takashi and Clemens:
> >
> > The snd-usb-audio driver has a race between close and disconnect. A
> > patch I have been testing reliably triggers this race
In commit 787f5627bec80094db487bfcb401e9744f181aed
usb: musb: make davinci and da8xx glues depend on BROKEN
USB_MUSB_DA8XX was marked as BROKEN
A few months ago, we updated the linux kernel on our AM1808 SoC based
embedded board from Linux 2.6.33 to the latest long term 3.12.
I am interested in
At Wed, 25 Jun 2014 10:59:29 -0400 (EDT),
Alan Stern wrote:
>
> On Wed, 25 Jun 2014, Takashi Iwai wrote:
>
> > [Adding Daniel to Cc]
> >
> > At Tue, 24 Jun 2014 13:52:14 -0400 (EDT),
> > Alan Stern wrote:
> > >
> > > Takashi and Clemens:
> > >
> > > The snd-usb-audio driver has a race between
Hi,
On Wed, Jun 25, 2014 at 10:13 AM, Jon Ringle wrote:
> In commit 787f5627bec80094db487bfcb401e9744f181aed
> usb: musb: make davinci and da8xx glues depend on BROKEN
>
> USB_MUSB_DA8XX was marked as BROKEN
>
> A few months ago, we updated the linux kernel on our AM1808 SoC based
> embedded boar
W dniu 25.06.2014 17:13, Jon Ringle pisze:
In commit 787f5627bec80094db487bfcb401e9744f181aed
usb: musb: make davinci and da8xx glues depend on BROKEN
USB_MUSB_DA8XX was marked as BROKEN
A few months ago, we updated the linux kernel on our AM1808 SoC based
embedded board from Linux 2.6.33 to th
Hi Paul,
I was wondering if you have ever tested this driver with a USB/ethernet
dongle? I'm using the apple usb/ethernet dongle, which is basically just
the ASIX AX88xxx Based Ethernet Adapter. From brief debugging, it
appears that Bulk and Interrupt endpoint data are getting corrupted
durin
On Wed, Jun 25, 2014 at 11:35 AM, Andrzej Pietrasiewicz
wrote:
> W dniu 25.06.2014 17:13, Jon Ringle pisze:
>
>> In commit 787f5627bec80094db487bfcb401e9744f181aed
>> usb: musb: make davinci and da8xx glues depend on BROKEN
>>
>> USB_MUSB_DA8XX was marked as BROKEN
>>
>> A few months ago, we updat
Use attribute-groups to fix race condition.
Signed-off-by: Janne Kanniainen
---
.../ABI/testing/sysfs-class-hid-driver-gt683r | 6 +++--
drivers/hid/hid-gt683r.c | 31 +-
2 files changed, 22 insertions(+), 15 deletions(-)
diff --git a/Document
From: Dinh Nguyen
> I was wondering if you have ever tested this driver with a USB/ethernet
> dongle? I'm using the apple usb/ethernet dongle, which is basically just
> the ASIX AX88xxx Based Ethernet Adapter. From brief debugging, it
> appears that Bulk and Interrupt endpoint data are getting corr
On Wed, Jun 25, 2014 at 06:59:26PM +0300, Janne Kanniainen wrote:
> Use attribute-groups to fix race condition.
The primary thing you're doing here is moving and renaming the attribute
to the led class devices, so you need to mention that (and update the
patch subject). But you can mention the rac
06/25/2014 02:34 PM, Daniele Forsi пишет:
2014-06-25 6:46 GMT+02:00 Evgeny Boger:
There might be 11 GPIOs in total.
do you mean "12 GPIOs"? You say later they are 0-based and the last one is "11"
Last three GPIOs (offsets 8-11, 0-based) are shared with FDX, LNKA, SPD
LEDs respectively.
Move led_mode attribute from HID device to led-class devices and rename it
msi_mode. This will also fix race condition by using attribute-groups.
Signed-off-by: Janne Kanniainen
---
Changes in v3:
- Style fixes
- Rename sysfs-class-hid-driver-gt683r to sysfs-class-leds-driver-gt6
From: "Sean O. Stalley"
Change the default wMaxPacketSize value for EP0 of Full Speed
devices from the maximum possible size (64) to the minimum (8).
All full speed devices support a packet size of 8, but not all
support a size of 64.
No packet longer than 8 bytes is ever read from EP0 before th
> From: Dinh Nguyen [mailto:dinh.li...@gmail.com]
> Sent: Wednesday, June 25, 2014 8:52 AM
>
> I was wondering if you have ever tested this driver with a USB/ethernet
> dongle? I'm using the apple usb/ethernet dongle, which is basically just
> the ASIX AX88xxx Based Ethernet Adapter. From brief de
On Wed, 25 Jun 2014, Sean O. Stalley wrote:
> From: "Sean O. Stalley"
>
> Change the default wMaxPacketSize value for EP0 of Full Speed
> devices from the maximum possible size (64) to the minimum (8).
> All full speed devices support a packet size of 8, but not all
> support a size of 64.
You
On Wed, 25 Jun 2014, Johan Hovold wrote:
> Did you see the attribute-race series I posted? Not sure how best to
> handle the dependency, as those patches should probably go in through
> the LEDs tree, while the first patch in that series (adding the groups
> field) is a dependency for this patch.
Mark Rutland writes:
> On Sun, Jun 22, 2014 at 10:04:58AM +0100, Robert Jarzmik wrote:
>> index 79729a9..0e4863f 100644
>> --- a/Documentation/devicetree/bindings/usb/pxa-usb.txt
>> +++ b/Documentation/devicetree/bindings/usb/pxa-usb.txt
>> @@ -29,3 +29,23 @@ Example:
>> marvell,port
Mark Rutland writes:
> On Sun, Jun 22, 2014 at 10:04:57AM +0100, Robert Jarzmik wrote:
>> +/**
>> + * pxa_udc_probe_dt - device tree specific probe
>> + * @pdev: platform data
>> + * @udc: pxa_udc structure to fill
>> + *
>> + * Fills udc from platform data out of device tree.
>> + *
>> + * Retur
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Wednesday, June 25, 2014 11:46 AM
> To: Stalley, Sean
> Cc: linux-usb@vger.kernel.org; Ismail, Abdul R
> Subject: Re: [PATCH] Change wMaxPacketSize default value for Full Speed EP0
>
> On Wed, 25 Jun 2014, S
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> Add new bindings used for USB support by the Tegra XUSB pad controller.
> This includes additional PHY types, USB-specific pinconfig properties, etc.
> diff --git
> a/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt
> b/
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> Add device-tree bindings for the Tegra XUSB mailbox which will be used
> for communication between the Tegra XHCI controller and the host.
Sorry for the slow review.
> diff --git
> a/Documentation/devicetree/bindings/mailbox/nvidia,tegra124-xusb
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> Add device-tree binding documentation for the XHCI controller present
> on Tegra124 and later SoCs.
> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra124-xhci.txt
> b/Documentation/devicetree/bindings/usb/nvidia,tegra124-xhci.txt
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> Add device-tree binding documentation for the XHCI controller present
> on Tegra124 and later SoCs.
> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra124-xhci.txt
> b/Documentation/devicetree/bindings/usb/nvidia,tegra124-xhci.txt
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> The Tegra XHCI controller communicates requests to the host through
> a mailbox interface. Host drivers which can handle these requests,
> such as the Tegra XUSB pad controller driver and upcoming Tegra XHCI
> host controller driver, can send mess
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> In addition to the PCIe and SATA PHYs, the XUSB pad controller also
> supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
> PCIe or SATA lane and is mapped to one of the three UTMI ports.
>
> diff --git a/drivers/pinctrl/pinctr
Thanks for the review Stephen!
On Wed, Jun 25, 2014 at 2:46 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> Add new bindings used for USB support by the Tegra XUSB pad controller.
>> This includes additional PHY types, USB-specific pinconfig properties, etc.
>
>> d
On Wed, Jun 25, 2014 at 2:42 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> Add device-tree bindings for the Tegra XUSB mailbox which will be used
>> for communication between the Tegra XHCI controller and the host.
>
> Sorry for the slow review.
>
>> diff --git
>
On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
> Add support for the on-chip XHCI host controller present on Tegra SoCs.
>
> The driver is currently very basic: it loads the controller with its
> firmware, starts the controller, and is able to service messages sent
> by the controller's firmware
On Wed, Jun 25, 2014 at 12:09 PM, Jiri Kosina wrote:
> On Wed, 25 Jun 2014, Johan Hovold wrote:
>
>> Did you see the attribute-race series I posted? Not sure how best to
>> handle the dependency, as those patches should probably go in through
>> the LEDs tree, while the first patch in that series
On 06/25/2014 04:37 PM, Andrew Bresticker wrote:
> On Wed, Jun 25, 2014 at 2:42 PM, Stephen Warren wrote:
>> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>>> Add device-tree bindings for the Tegra XUSB mailbox which will be used
>>> for communication between the Tegra XHCI controller and the h
On Wed, Jun 25, 2014 at 2:52 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> Add device-tree binding documentation for the XHCI controller present
>> on Tegra124 and later SoCs.
>
>> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra124-xhci.txt
>> b/D
On Wed, Jun 25, 2014 at 2:54 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> Add device-tree binding documentation for the XHCI controller present
>> on Tegra124 and later SoCs.
>
>> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra124-xhci.txt
>> b/D
On Wed, Jun 25, 2014 at 3:02 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> The Tegra XHCI controller communicates requests to the host through
>> a mailbox interface. Host drivers which can handle these requests,
>> such as the Tegra XUSB pad controller driver an
On 06/25/2014 05:01 PM, Andrew Bresticker wrote:
> On Wed, Jun 25, 2014 at 2:52 PM, Stephen Warren wrote:
>> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>>> Add device-tree binding documentation for the XHCI controller present
>>> on Tegra124 and later SoCs.
>>
>>> diff --git a/Documentation/
On 06/25/2014 05:02 PM, Andrew Bresticker wrote:
> On Wed, Jun 25, 2014 at 2:54 PM, Stephen Warren wrote:
>> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>>> Add device-tree binding documentation for the XHCI controller present
>>> on Tegra124 and later SoCs.
>>
>>> diff --git a/Documentation/
On Wed, Jun 25, 2014 at 3:12 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> In addition to the PCIe and SATA PHYs, the XUSB pad controller also
>> supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
>> PCIe or SATA lane and is mapped to one of th
On Wed, Jun 25, 2014 at 3:37 PM, Stephen Warren wrote:
> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>> Add support for the on-chip XHCI host controller present on Tegra SoCs.
>>
>> The driver is currently very basic: it loads the controller with its
>> firmware, starts the controller, and is
Hi Felipe,
(2014/06/18 14:15), Magnus Damm wrote:
> Hi Felipe,
>
> On Fri, Jun 13, 2014 at 11:25 PM, Felipe Balbi wrote:
>> Hi,
>>
>> On Fri, Jun 13, 2014 at 09:20:31PM +0900, Yoshihiro Shimoda wrote:
< snip >
>>> +/* This function needs to initialize a "phy" of usb before */
>>
>> initializing
> > This patch is to enable USB host controller for Intel Quark X1000. Add
> > pci quirks to adjust the packet buffer in/out threshold value, and
> > ensure EHCI packet buffer i/o threshold value is reconfigured to half.
>
> Please add more detailed description. For example, why is it necessary to
> >
> > OK, I will change ' usb_is_intel_qrk ' to ' usb_is_intel_quark'.
>
> Or even usb_is_intel_quark_x1000() ?
>
OK, I will change the function name as your suggestion to make it more specific.
> David
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the
On Wed, Jun 25, 2014 at 11:52 AM, Jon Ringle wrote:
> On Wed, Jun 25, 2014 at 11:35 AM, Andrzej Pietrasiewicz
> wrote:
>> W dniu 25.06.2014 17:13, Jon Ringle pisze:
>>
>>> In commit 787f5627bec80094db487bfcb401e9744f181aed
>>> usb: musb: make davinci and da8xx glues depend on BROKEN
>>>
>>> USB_M
On Wed, Jun 25, 2014 at 09:11:25PM +, Stalley, Sean wrote:
> > > Changing the default max packet
> > > size to 8 helps clarify that.
> >
> > No. Did you test this patch with full-speed devices having various
> > maxpacket
> > sizes?
> >
>
> I was waiting for feedback on the patch before I
Greg,
You are right, we need to do our work first before sending in patches.
Sean,
Let's synch up when I am back in the office and we can determine next steps.
Thanks!
Rahman
USB-IF CTO and Compliance Chair
> On Jun 25, 2014, at 10:50 PM, "Greg KH" wrote:
>
> On Wed, Jun 25, 2014 at 09:11:25P
> > This patch is to enable USB host controller for Intel Quark X1000. Add
>> pci quirks to adjust the packet buffer in/out threshold value, and
> >ensure EHCI packet buffer i/o threshold value is reconfigured to half
>
>
> What is the packet buffer in/out threshold value and why does it need to
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers as user selectable. Instead select them from
the respective USB configs to make things easier for the end user.
While at it enable 5250 phy f
USB DWC3 driver on Exynos platforms does not work without its
corresponding phy driver. Hence it makes no sense to keep the
phy driver as user selectable. Instead select it from USB config
to make things easier for the end user.
While at it make the config depend on ARCH_EXYNOS5 instead of
ARCH_EXY
On 06/26/2014 11:09 AM, Sachin Kamat wrote:
> EHCI and OHCI drivers on Exynos platforms do not work without their
> corresponding SoC specific phy drivers. Hence it makes no sense to
> keep these phy drivers as user selectable. Instead select them from
> the respective USB configs to make things ea
On 06/26/2014 11:09 AM, Sachin Kamat wrote:
> USB DWC3 driver on Exynos platforms does not work without its
> corresponding phy driver. Hence it makes no sense to keep the
> phy driver as user selectable. Instead select it from USB config
> to make things easier for the end user.
> While at it make
Hi Jon,
On Thu, Jun 26, 2014 at 4:46 AM, Jon Ringle wrote:
> The only thing I needed to do was to remove the
> BROKEN dependency on USB_MUSB_DA8XX. Is there anything else I would
> have to do besides just removing BROKEN to get this accepted back into
> the kernel source tree?
I tried to remove
73 matches
Mail list logo
