From: mail@beyermatthias.de (Matthias Beyer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to test my patches for the (staging) android driver?
Date: Wed, 4 Dec 2013 19:53:36 +0100 [thread overview]
Message-ID: <20131204185336.GG2264@fu> (raw)
In-Reply-To: <4806.1386170243@turing-police.cc.vt.edu>
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
prev parent reply other threads:[~2013-12-04 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131203151642.GB2264@fu>
2013-12-03 15:57 ` How to test my patches for the (staging) android driver? Matthias Beyer
2013-12-04 15:08 ` Matthias Beyer
2013-12-04 15:17 ` Valdis.Kletnieks at vt.edu
2013-12-04 18:53 ` Matthias Beyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131204185336.GG2264@fu \
--to=mail@beyermatthias.de \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.