July 2016 - kernelnewbies@kernelnewbies.org - Kernelnewbies Mailing Lists

Re: Replying to E-mails I did not receive
by Peter Senna Tschudin July 3, 2016

July 3, 2016

On Jul 3, 2016 17:10, <Valdis.Kletnieks(a)vt.edu> wrote: > > On Sun, 03 Jul 2016 13:10:42 +0200, Peter Senna Tschudin said: > > Hi! > > > > I tested a few patches sent to lists I'm not subscribed to. I want to > > reply to the thread with my "Tested-by: " and "Acked-by:", but I'm not > > sure what is the best way to do it. > > > > Is it enough to simply compose a new message with the original text as > > a reply to the correct message id? > > Why not just do a 'reply all' and let your mail software do the heavy lifting? > It's always worked for me.... Because I don't have the emails. I downloaded the patches from the mailing list web page...

1 0

Replying to E-mails I did not receive
by Peter Senna Tschudin July 3, 2016

July 3, 2016

Hi! I tested a few patches sent to lists I'm not subscribed to. I want to reply to the thread with my "Tested-by: " and "Acked-by:", but I'm not sure what is the best way to do it. Is it enough to simply compose a new message with the original text as a reply to the correct message id? How you usually do that? Thank you! Peter -- Peter

1 0

Kernel Version 4.6.3 - build error
by Michael McCann July 2, 2016

July 2, 2016

Has anyone seen this problem when building 4.6.3? Mike KB2GHZ * HOSTCC scripts/recordmcount HOSTCC scripts/sortextable HOSTCC scripts/asn1_compiler HOSTCC scripts/sign-filescripts/sign-file.c:25:30: fatal error: openssl/opensslv.h: No such file or directory #include <openssl/opensslv.h> ^compilation terminated.make[1]: *** [scripts/sign-file] Error 1make: *** [scripts] Error 2real 0m13.452suser 0m8.704ssys 0m5.631s*

2 2

convension about type argument on _IO macro
by Colin Vidal July 2, 2016

July 2, 2016

Hi all, In LDDv3, chapter 6, on ioctl, macros IOCTQUANTIUM is defined with _IO(SCULL_MAGIC, 3). IOCT_* tells that a value (given directly as value through the argument) is set to the device. However, no type is given to this macro. It is not a big deal since this macro is just a helper to generate identifiers, but, I wonder if there is any convention telling that we should precise an argument only if it's a pointer ? Thanks - Colin

1 0

no device creation by udev
by anno79＠mailbox.org July 1, 2016

July 1, 2016

I have written the following lines of code to get a char device working. ( lines with # indicate that I have tried versions of this code snippet without them) class_hello = class_create(THIS_MODULE, device_name); # class_hello->devnode = &hello_devnode; retval = alloc_chrdev_region( &dev_file, 0, 1, device_name ); cdev_init( &device, &file_ops ); # device.owner = THIS_MODULE; # kobject_set_name(&device.kobj, device_name); cdev_add( &device, MKDEV(dev_file, 0), 1 ) device = device_create( class_hello, NULL, MKDEV(dev_file, 0), NULL, device_name ); # kobj_device->devt = MKDEV(dev_file, 0); Make it open / close / read / write works fine - but look at that $ ls /sys/class/hello/hello power subsystem uevent The "dev" entry is missing - and udev does not react. Anybody knows what is else needed to make udev react?

2 1