On Sun, Feb 21, 2016 at 2:17 PM, Diego Viola wrote:
> On Sun, Feb 21, 2016 at 9:45 AM, One Thousand Gnomes
> wrote:
>>> I would appreciate some hint from someone who is more experienced with
>>> drivers.
>>
>> Start by testing
>>
>> - loading the driver as a module
>> - using the networking
>> -
On Sun, Feb 21, 2016 at 9:45 AM, One Thousand Gnomes
wrote:
>> I would appreciate some hint from someone who is more experienced with
>> drivers.
>
> Start by testing
>
> - loading the driver as a module
> - using the networking
> - unloading the module (and checking it stays unloaded!)
>
> then
On Sat, Feb 20, 2016 at 10:16 PM, David Miller wrote:
>
> Sorry, this is not how things work.
>
> You can suggest marking the driver unmaintained in MAINTAINERS if the
> listed developer has been unresponsive for a very long time.
>
> But removing the driver altogether is not prudent at all.
>
> J
Sorry, this is not how things work.
You can suggest marking the driver unmaintained in MAINTAINERS if the
listed developer has been unresponsive for a very long time.
But removing the driver altogether is not prudent at all.
Just because it doesn't work %100 the way you like, and nobody
has wor
4 matches
Mail list logo