From mboxrd@z Thu Jan  1 00:00:00 1970
From: mail@beyermatthias.de (Matthias Beyer)
Date: Wed, 4 Dec 2013 19:53:36 +0100
Subject: How to test my patches for the (staging) android driver?
In-Reply-To: <4806.1386170243@turing-police.cc.vt.edu>
References: <20131203151642.GB2264@fu> <20131203155708.GD2264@fu>
	<20131204150852.GF2264@fu>
	<4806.1386170243@turing-police.cc.vt.edu>
Message-ID: <20131204185336.GG2264@fu>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On 04-12-2013 10:17:23, Valdis.Kletnieks at vt.edu wrote:
> On Wed, 04 Dec 2013 16:08:52 +0100, Matthias Beyer said:
> 
> > > > 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?
> 
> If at all possible, you should cross-compile for an appropriate architecture
> and actually boot and test the code in question.  There's lots of ways
> to write code in C that compiles cleanly, looks correct, but is subtly
> wrong for some reason.

Thank you for your reply!

How to cross-compile and even more important: How to test? I
do not have devices for testing! Should I try it in a VM?

What I can do is checking if the object file is the same before and
after my stylefix patches. But I think this does not work for
functions I split up into several smaller ones...

-- 
Mit freundlichen Gr??en,
Kind regards,
Matthias Beyer

Proudly sent with mutt.
Happily signed with gnupg.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131204/7e8fbbe1/attachment-0001.bin