netdev - Re: [PATCH] asix: new device id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANEJEGtiHZRzQgGnBDZnuGvuZOfXxwcDdB9XdxYgO1zY7O_GVw@mail.gmail.com>
Date:	Mon, 19 Dec 2011 13:34:24 -0800
From:	Grant Grundler <grundler@...omium.org>
To:	David Miller <davem@...emloft.net>
Cc:	aurel@...age.org, netdev@...r.kernel.org, allan@...x.com.tw,
	freddy@...x.com.tw
Subject: Re: [PATCH] asix: new device id

On Mon, Dec 19, 2011 at 1:25 PM, David Miller <davem@...emloft.net> wrote:
> From: Grant Grundler <grundler@...gle.com>
> Date: Mon, 19 Dec 2011 13:22:35 -0800
>
>> I'm really the wrong guy to ask though. I don't have the device
>> and I'm not associated with the mfg.
>
> Strongly disagree.
>
> When you make changes to a driver, in fact you've made the most
> recent 5 or 6, it's like "tag, you're it" :-)

Fair enough. :)   But I'm trying to change that. :) (Have ASIX to
participate in asix.c devel/support).


Acked-by: Grant Grundler <grundler@...omium.org>

The change is "harmless" in that it won't interfere with anything that
works today.

> Just so you understand why I am not going to ask random people who
> have never submitted a change to the driver whether a change makes
> sense or not.

Understood. But I have no clue what driver functionality *will* work
with the new device.
I guess this is the first step to finding out. :)

cheers,
grant
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html