From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
Subject: Re: [PATCHv1 2/3] tests: build tests by default
Date: Tue, 05 Apr 2011 15:45:22 +0300 [thread overview]
Message-ID: <1302007522.2760.123.camel@localhost> (raw)
In-Reply-To: <BANLkTimsfEKUMGBAfyLoeqSQnB-6u-jWPw@mail.gmail.com>
On Tue, 2011-04-05 at 08:44 -0400, Josh Boyer wrote:
> On Tue, Apr 5, 2011 at 7:33 AM, Andy Shevchenko
> <ext-andriy.shevchenko@nokia.com> wrote
> >
> > -install:: ${TARGETS} ${SCRIPTS}
> > +install:: ${TARGETS} ${SCRIPTS} tests
> > mkdir -p ${DESTDIR}/${SBINDIR}
> > install -m 0755 ${TARGETS} ${SCRIPTS} ${DESTDIR}/${SBINDIR}/
> > mkdir -p ${DESTDIR}/${MANDIR}/man1
> > diff --git a/tests/Makefile b/tests/Makefile
> > new file mode 100644
> > index 0000000..05b37e9
> > --- /dev/null
> > +++ b/tests/Makefile
> > @@ -0,0 +1,8 @@
> > +
> > +SUBDIRS = checkfs fs-tests jittertest ubi-tests
> > +
> > +all clean tests: $(SUBDIRS)
> > +
> > +.PHONY: $(SUBDIRS)
> > +$(SUBDIRS):
> > + $(MAKE) -C $@ $(MAKECMDGOALS)
>
> We don't want the tests installed by default, do we? If we do for
> some reason, it might be better to stick them in
> /usr/libexec/mtd-utils/ or /usr/share/mtd-utils/ or something. I
> doubt we need them sitting in /usr/sbin,/sbin,/bin,/usr/bin on 99% of
> the installs.
I agree that installing tests should be a separate option.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-05 12:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 11:33 [PATCHv1 1/3] tests: make jittertest buildable Andy Shevchenko
2011-04-05 11:33 ` [PATCHv1 2/3] tests: build tests by default Andy Shevchenko
2011-04-05 12:44 ` Josh Boyer
2011-04-05 12:45 ` Artem Bityutskiy [this message]
2011-04-05 12:57 ` Florian Fainelli
2011-04-05 15:03 ` [PATCHv2] tests: introduce new target tests in Makefile Andy Shevchenko
2011-04-06 8:53 ` Artem Bityutskiy
2011-04-06 9:04 ` Florian Fainelli
2011-04-07 10:44 ` Artem Bityutskiy
2011-04-07 13:10 ` Andy Shevchenko
2011-04-07 13:10 ` Artem Bityutskiy
2011-04-07 13:27 ` Andy Shevchenko
2011-04-07 13:44 ` Artem Bityutskiy
2011-04-05 11:33 ` [PATCHv1 3/3] tests: fix compiler warnings Andy Shevchenko
2011-04-05 12:52 ` Artem Bityutskiy
2011-04-05 13:08 ` Andy Shevchenko
2011-04-05 13:55 ` [PATCHv1 1/5] tests: checkfs: " Andy Shevchenko
2011-04-05 13:55 ` [PATCHv1 2/5] tests: checkfs: fix linker warnings Andy Shevchenko
2011-04-05 14:15 ` Artem Bityutskiy
2011-04-05 13:55 ` [PATCHv1 3/5] tests: fs-tests: check return value of functions Andy Shevchenko
2011-04-05 14:17 ` Artem Bityutskiy
2011-04-05 13:55 ` [PATCHv1 4/5] tests: jittertest: fix set of compiler warnings Andy Shevchenko
2011-04-05 14:20 ` Artem Bityutskiy
2011-04-05 14:32 ` [PATCHv2] " Andy Shevchenko
2011-04-05 14:39 ` Artem Bityutskiy
2011-04-05 13:55 ` [PATCHv1 5/5] tests: ubi-tests: seed_random_generator() was used w/o prototype Andy Shevchenko
2011-04-05 14:22 ` Artem Bityutskiy
2011-04-05 14:08 ` [PATCHv1 1/5] tests: checkfs: fix compiler warnings Artem Bityutskiy
2011-04-05 12:51 ` [PATCHv1 1/3] tests: make jittertest buildable Artem Bityutskiy
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=1302007522.2760.123.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=ext-andriy.shevchenko@nokia.com \
--cc=jwboyer@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 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.