Ah, Now I understand, Thunderbird somehow chooses application/octet as type for C-source code. Reattaching this time as .txt file. About patch vs c-code file, I don't have any changes to the kernel build system, one of the blessings of the new buildsystem is that it is very easy to build modules out of tree and that is what I've been doing I've also attached a Makefile.txt for you to build it with. Thanks & Regards, Hans Jean Delvare wrote: >>>>The driver. >>> >>>-ENOPATCH >> >>Yes, its a new driver, so nothing to diff against, would a diff against >>/dev/null really make you happier? > > > No, I mean, there is no attachement at all. > > And yes, a patch would still make me happier, because it would include > the relevant changes to the kernel build system so that we can check > that your code compiles properly, and people could test your driver > more easily too. > > >>Can someone please take a look at the driver and give me some proper >>feedback? > > > Not before you actually send something to us ;) > > Note that the mailing list is configured to drop any unacceptable > attachement. Maybe that's what happened. Accepted types are text/plain > and text/x-patch. Make sure your attachement has the proper type. If > you think there is a different type we should accept, please let us > know. > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: abituguru.txt Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20051021/ed48dec3/attachment.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Makefile.txt Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20051021/ed48dec3/attachment-0001.txt
