From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd stresstest: Fix random number generation
Date: Fri, 25 May 2012 17:57:15 +0300 [thread overview]
Message-ID: <1337957835.30969.45.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1337954309-18178-1-git-send-email-s.hauer@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Fri, 2012-05-25 at 15:58 +0200, Sascha Hauer wrote:
> the random number generation in the mtd stresstest was changed from a
> homebrew generator to random32. random32 generates unsigned random
> numbers, but the values are assigned to signed integers. This results
> in negative offsets, eraseblocks and writesized. Fix it by using unsigned
> integers for these variables instead.
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-25 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 13:58 [PATCH] mtd stresstest: Fix random number generation Sascha Hauer
2012-05-25 14:57 ` Artem Bityutskiy [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=1337957835.30969.45.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).