Re: [PATCH] added support for ASIX 88178 chipset USB Gigabit Ethernetadaptor

[Eduard Warkentin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hi Greg!

First of all, i hope you arent angry about having me sent this reply
as CC to the current maintainer and to the mailing list. If so, I
apologize, and it wont happen in future.

> Hm, your tabs and spaces are messed up :(
I reviewed the original file again, and the lines just above mine
indeed have spare leading whitespaces. Shall  I include changing them
in my patch? I really dont know wether it just will ok, or will make
it harder to identify what i actually did in patch.  I have to excuse
myself for asking about those details, but this is my very first
kernel patch ever. (For now, I left the whitespaces as I found them in
the source file. Please, clue me on how to deal with those, wehen i
encounter them again.)

So, here's my corrected patch again:

FROM: Eduard Warkentin <eduard.warkentin@xxxxxx>

Added support for detetcion an dworking with a ASIX 88178 based
USB-Gigabit
adaptor. With the patch, it is detected and handled correctly by the asix
module.

Signed-off-by: Eduard Warkentin <eduard.warkentin@xxxxxx>

- --- ./drivers/usb/net/asix.c.orig 2006-03-20 06:53:29.000000000 +0100
+++ ./drivers/usb/net/asix.c  2006-05-18 01:18:52.000000000 +0200
@@ -913,6 +913,10 @@ static const struct usb_device_id  produc
         USB_DEVICE (0x0b95, 0x7720),
         .driver_info = (unsigned long) &ax88772_info,
 }, {
+  // ASIX AX88178 10/100/1000
+  USB_DEVICE (0x0b95, 0x1780),
+  .driver_info = (unsigned long) &ax88772_info,
+}, {
  // Linksys USB200M Rev 2
  USB_DEVICE (0x13b1, 0x0018),
  .driver_info = (unsigned long) &ax88772_info,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEbOyK0HvYPTIhdZcRA+rAAKCAChGPNe3lCaPcZUNkJujYJmmUZgCgq6tc
bTotPl6JBMbch/DpS9O0DEQ=
=1BCn
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/