From: Jared Hulbert <jaredeh@gmail.com>
To: MTD List <linux-mtd@lists.infradead.org>
Subject: Unit test for cfi_cmdset_0001.c
Date: Thu, 27 Jan 2005 17:20:49 -0800 [thread overview]
Message-ID: <6934efce05012717207271fb10@mail.gmail.com> (raw)
I plan on creating a unit test based on cutest.sourceforge.net for
cfi_cmdset_0001.c.
In order to stub out the various functions inside I will have to:
1. Manually strip out functions for each version.
2. Add #if''s
3. fork this file into 2-3 files.
I prefer option 3. As it seems cleaner to me and more maintainable.
But I want to know which option is more "commitable." Of course the
test be made availiable, I would hope we can get the tests commited
too. CuTest is zlib licenced. Is that a problem?
The reason for the unit tests is to help us find bugs in the code
paths not easily tested and to enable more rapid updates for new flash
or features mtd doesn't currently support.
Thoughts, flames, jokes?
,Jared
next reply other threads:[~2005-01-28 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 1:20 Jared Hulbert [this message]
2005-01-28 2:12 ` Unit test for cfi_cmdset_0001.c Nicolas Pitre
2005-01-28 2:16 ` Josh Boyer
2005-01-28 6:11 ` Eric W. Biederman
2005-01-28 19:47 ` Jared Hulbert
2005-01-28 20:59 ` Nicolas Pitre
2005-01-29 1:48 ` Jared Hulbert
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=6934efce05012717207271fb10@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox