How to test my patches for the (staging) android driver?
mail at beyermatthias.de
Wed Dec 4 10:08:52 EST 2013
As I do not get any answer from the other MLs, this goes here, too.
Maybe there is just too much noise in lkml... never mind!
On 03-12-2013 16:57:08, Matthias Beyer wrote:
> Greg-KHs email bot tells me to send this message to a ML. It suggests
> to send it to this list or kernelnewbies at nl.linux.org, but the latter
> results in a failure notice. So I send this email to this list.
> On 03-12-2013 16:16:42, Matthias Beyer wrote:
> > Hi,
> > First: I'm really new to the kernel in manner of submitting patches,
> > testing etc. Please, if you send me guidelines or pointers on
> > what to do, explain how to do things!
> > I'm working on some cleanup patches for code in drivers/staging/android/.
> > These patches are cleanup patches as suggested in the appropriate TODO
> > file, including fixes for checkpatch, but also function splitting as
> > there are some really long functions (mainly in binder.c).
> > How to test my code beside compiling it? Do I even have a possibility
> > to test it or should I just send it to you?
> > Besides: Which ML should I post this (and the patches) to? Main Kernel
> > ML?
Mit freundlichen Grüßen,
Proudly sent with mutt.
Happily signed with gnupg.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131204/c647d318/attachment.bin
More information about the Kernelnewbies