From: Markus Kolb
Date: Sun, 06 May 2012 12:13:32 +0200
> David Miller wrote on 03.05.2012 07:11:
>> From: Markus Kolb
>> Date: Thu, 03 May 2012 06:57:39 +0200
>>
>>> I'll build it during next rainy day and will report its success
>>> after some usage ;-)
>>
>> Thank you.
>
> Works without any p
David Miller wrote on 03.05.2012 07:11:
From: Markus Kolb
Date: Thu, 03 May 2012 06:57:39 +0200
I'll build it during next rainy day and will report its success
after some usage ;-)
Thank you.
Works without any problem for me.
So maybe this patch will be included in the official kernels befo
Jonathan Nieder writes:
> Hi Iker,
>
> David Miller wrote:
>> From: Bjørn Mork
>> Date: Thu, 26 Apr 2012 14:35:10 +0200
>
>>> The same comments as for v1 regarding testing applies. This is build
>>> tested only. Should go through some functional testing before being
>>> applied.
>>
>> Well? I
From: Markus Kolb
Date: Thu, 03 May 2012 06:57:39 +0200
> I'll build it during next rainy day and will report its success
> after some usage ;-)
Thank you.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
David Miller schrieb:
>From: Bjørn Mork
>Date: Thu, 26 Apr 2012 14:35:10 +0200
>
>> The same comments as for v1 regarding testing applies. This is build
>> tested only. Should go through some functional testing before being
>> applied.
>
>Well? Is anyone gonna test this?
I'll build it duri
From: Bjørn Mork
Date: Thu, 26 Apr 2012 14:35:10 +0200
> The same comments as for v1 regarding testing applies. This is build
> tested only. Should go through some functional testing before being
> applied.
Well? Is anyone gonna test this?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ.
Hi Iker,
David Miller wrote:
> From: Bjørn Mork
> Date: Thu, 26 Apr 2012 14:35:10 +0200
>> The same comments as for v1 regarding testing applies. This is build
>> tested only. Should go through some functional testing before being
>> applied.
>
> Well? Is anyone gonna test this?
Looks like i
Some RNDIS devices include a bogus CDC Union descriptor pointing
to non-existing interfaces. The RNDIS code is already prepared
to handle devices without a CDC Union descriptor by hardwiring
the driver to use interfaces 0 and 1, which is correct for the
devices with the bogus descriptor as well. S
8 matches
Mail list logo