moved.
Destroying the tty_port will ensure that resources are
freed and modprobe will not hang.
Signed-off-by: Andre Wolokita
---
drivers/usb/gadget/function/u_serial.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/u_serial.c
b/drivers/usb/g
moved.
Destroying the tty_port will ensure that resources are
freed and modprobe will not hang.
Signed-off-by: Andre Wolokita
---
drivers/usb/gadget/function/u_serial.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/u_serial.c
b/drivers/usb/g
On 09/10/14 13:56, Greg KH wrote:
> On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
>> Issuing a modprobe -r g_serial command to the target
>> over the gadget serial communications line causes
>> modprobe to enter uninterruptable sleep, leaving the
>>
On 09/10/14 14:38, Greg KH wrote:
> On Thu, Oct 09, 2014 at 02:08:04PM +1100, Andre Wolokita wrote:
>> On 09/10/14 13:56, Greg KH wrote:
>>> On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
>>>> Issuing a modprobe -r g_serial command to the targ
On 10/10/14 00:47, Peter Hurley wrote:
> Hi Andre,
>
> On 10/08/2014 11:54 PM, Andre Wolokita wrote:
>> On 09/10/14 14:38, Greg KH wrote:
>>> On Thu, Oct 09, 2014 at 02:08:04PM +1100, Andre Wolokita wrote:
>>>> On 09/10/14 13:56, Greg KH wrote:
>>&g
Hi Felipe,
I'm noticing some strange behaviour in the gadgetfs driver when running
gadgetfs-test; the program fails with the error "ep0 read after poll: Invalid
argument".
As far as I understand, an inode is created upon an open() call in
gadgetfs-test and
an initial fops is assigned to the str
Hi Felipe,
I'm noticing some strange behaviour in the gadgetfs driver when running
gadgetfs-test; the program fails with the error "ep0 read after poll: Invalid
argument".
As far as I understand, an inode is created upon an open() call in
gadgetfs-test and
an initial fops is assigned to the str
Hi Felipe,
On 28/10/14 01:26, Felipe Balbi wrote:
> Hi,
>
> On Mon, Oct 27, 2014 at 10:31:42AM +1100, Andre Wolokita wrote:
>> I'm noticing some strange behaviour in the gadgetfs driver when
>> running gadgetfs-test; the program fails with the error "ep0 read