public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
To: Artem.Bityutskiy@nokia.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCHv1 3/3] tests: fix compiler warnings
Date: Tue, 05 Apr 2011 16:08:25 +0300	[thread overview]
Message-ID: <1302008905.29819.127.camel@fs-test.research.nokia.com> (raw)
In-Reply-To: <1302007944.2760.126.camel@localhost>

On Tue, 2011-04-05 at 15:52 +0300, Artem Bityutskiy wrote:
> On Tue, 2011-04-05 at 14:33 +0300, Andy Shevchenko wrote:
> > Signed-off-by: Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
> > ---
> >  tests/checkfs/checkfs.c              |    8 ++++----
> >  tests/checkfs/comm.c                 |    2 +-
> >  tests/fs-tests/lib/tests.c           |    3 ++-
> >  tests/fs-tests/stress/atoms/pdfrun.c |    5 ++++-
> >  tests/jittertest/JitterTest.c        |   11 ++++++++---
> >  tests/ubi-tests/integ.c              |    5 +++--
> >  6 files changed, 22 insertions(+), 12 deletions(-)
> 
> Would it please be possible to split this patch on a series of per-test
> patches and may be write which warnings are fixed. For some of the
> changes it is difficult to figure out what is being fixed.
Makes sense. Will do.


-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2011-04-05 13:07 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
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 [this message]
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=1302008905.29819.127.camel@fs-test.research.nokia.com \
    --to=ext-andriy.shevchenko@nokia.com \
    --cc=Artem.Bityutskiy@nokia.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