All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: <computersforpeace@gmail.com>, <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, akinobu.mita@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] mtd: mtd_oobtest: fix bitflip_limit usage in test case 3
Date: Tue, 31 Mar 2015 11:28:14 +0300	[thread overview]
Message-ID: <551A5A9E.80402@ti.com> (raw)
In-Reply-To: <1417792720-3017-1-git-send-email-rogerq@ti.com>

Hi,

On 05/12/14 17:18, Roger Quadros wrote:
> Hi,
> 
> The bitflip_limit parameter was recently introduced to oobtest.
> However, it didn't implement the bitflip_limit check for all cases in test case 3.
> Patch 1 tackles the missed scenarios in test case 3, to adhere to bitflip_limit parameter.
> 
> Patch 2 extends the memory compare helper so that we can pass a non-zero offset to be
> printed in the error message. This is useful in the vary_offset case when we need to
> compare only a section of the OOB available block.

Gentle reminder to review and pick these. Thanks.

cheers,
-roger

> 
> --
> cheers,
> -roger
> 
> Roger Quadros (2):
>   mtd: mtd_oobtest: Fix bitflip_limit usage in test case 3
>   mtd: mtd_oobtest: Fix the address offset with vary_offset case
> 
>  drivers/mtd/tests/oobtest.c | 79 ++++++++++++++++++++++++++-------------------
>  1 file changed, 46 insertions(+), 33 deletions(-)
> 

WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: <computersforpeace@gmail.com>, <dwmw2@infradead.org>
Cc: <akinobu.mita@gmail.com>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] mtd: mtd_oobtest: fix bitflip_limit usage in test case 3
Date: Tue, 31 Mar 2015 11:28:14 +0300	[thread overview]
Message-ID: <551A5A9E.80402@ti.com> (raw)
In-Reply-To: <1417792720-3017-1-git-send-email-rogerq@ti.com>

Hi,

On 05/12/14 17:18, Roger Quadros wrote:
> Hi,
> 
> The bitflip_limit parameter was recently introduced to oobtest.
> However, it didn't implement the bitflip_limit check for all cases in test case 3.
> Patch 1 tackles the missed scenarios in test case 3, to adhere to bitflip_limit parameter.
> 
> Patch 2 extends the memory compare helper so that we can pass a non-zero offset to be
> printed in the error message. This is useful in the vary_offset case when we need to
> compare only a section of the OOB available block.

Gentle reminder to review and pick these. Thanks.

cheers,
-roger

> 
> --
> cheers,
> -roger
> 
> Roger Quadros (2):
>   mtd: mtd_oobtest: Fix bitflip_limit usage in test case 3
>   mtd: mtd_oobtest: Fix the address offset with vary_offset case
> 
>  drivers/mtd/tests/oobtest.c | 79 ++++++++++++++++++++++++++-------------------
>  1 file changed, 46 insertions(+), 33 deletions(-)
> 


  parent reply	other threads:[~2015-03-31  8:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 15:18 [PATCH 0/2] mtd: mtd_oobtest: fix bitflip_limit usage in test case 3 Roger Quadros
2014-12-05 15:18 ` Roger Quadros
2014-12-05 15:18 ` [PATCH 1/2] mtd: mtd_oobtest: Fix " Roger Quadros
2014-12-05 15:18   ` Roger Quadros
2015-04-06  1:12   ` Brian Norris
2015-04-06  1:12     ` Brian Norris
2014-12-05 15:18 ` [PATCH 2/2] mtd: mtd_oobtest: Fix the address offset with vary_offset case Roger Quadros
2014-12-05 15:18   ` Roger Quadros
2015-04-02 16:26   ` Brian Norris
2015-04-02 16:26     ` Brian Norris
2015-04-09 11:16     ` [PATCH v2 " Roger Quadros
2015-04-09 11:16       ` Roger Quadros
2015-03-31  8:28 ` Roger Quadros [this message]
2015-03-31  8:28   ` [PATCH 0/2] mtd: mtd_oobtest: fix bitflip_limit usage in test case 3 Roger Quadros

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=551A5A9E.80402@ti.com \
    --to=rogerq@ti.com \
    --cc=akinobu.mita@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.