From: Brian Norris <computersforpeace@gmail.com>
To: "zhaoxiu.zeng" <zhaoxiu.zeng@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 21/31] mtd: use parity16 in ssfdc.c
Date: Fri, 1 Apr 2016 16:48:50 -0700 [thread overview]
Message-ID: <20160401234850.GM2545@google.com> (raw)
In-Reply-To: <56F78ACB.1010402@gmail.com>
On Sun, Mar 27, 2016 at 03:24:59PM +0800, zhaoxiu.zeng wrote:
> From: Zeng Zhaoxiu <zhaoxiu.zeng@gmail.com>
>
> Signed-off-by: Zeng Zhaoxiu <zhaoxiu.zeng@gmail.com>
I'm not CC'd on the rest of this series, where you defined parity16().
And I doubt you've tested this. So I'm not applying.
Brian
> drivers/mtd/ssfdc.c | 20 ++------------------
> 1 file changed, 2 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/mtd/ssfdc.c b/drivers/mtd/ssfdc.c
> index daf82ba..b4d9144 100644
> --- a/drivers/mtd/ssfdc.c
> +++ b/drivers/mtd/ssfdc.c
> @@ -182,24 +182,10 @@ static int read_raw_oob(struct mtd_info *mtd, loff_t offs, uint8_t *buf)
> return 0;
> }
>
> -/* Parity calculator on a word of n bit size */
> -static int get_parity(int number, int size)
> -{
> - int k;
> - int parity;
> -
> - parity = 1;
> - for (k = 0; k < size; k++) {
> - parity += (number >> k);
> - parity &= 1;
> - }
> - return parity;
> -}
> -
> /* Read and validate the logical block address field stored in the OOB */
> static int get_logical_address(uint8_t *oob_buf)
> {
> - int block_address, parity;
> + int block_address;
> int offset[2] = {6, 11}; /* offset of the 2 address fields within OOB */
> int j;
> int ok = 0;
> @@ -215,11 +201,9 @@ static int get_logical_address(uint8_t *oob_buf)
>
> /* Check for the signature bits in the address field (MSBits) */
> if ((block_address & ~0x7FF) == 0x1000) {
> - parity = block_address & 0x01;
> block_address &= 0x7FF;
> - block_address >>= 1;
>
> - if (get_parity(block_address, 10) != parity) {
> + if (!parity16(block_address)) {
> pr_debug("SSFDC_RO: logical address field%d"
> "parity error(0x%04X)\n", j+1,
> block_address);
> --
> 2.5.5
>
next prev parent reply other threads:[~2016-04-01 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458788612-4367-1-git-send-email-zhaoxiu.zeng@gmail.com>
2016-03-27 7:24 ` [PATCH 21/31] mtd: use parity16 in ssfdc.c zhaoxiu.zeng
2016-04-01 23:48 ` Brian Norris [this message]
2016-03-27 7:27 ` [PATCH 22/31] mtd: use parity functions in inftlcore.c zhaoxiu.zeng
2016-03-27 7:33 ` [PATCH 24/31] mtd: use parity16 in sm_ftl.c zhaoxiu.zeng
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=20160401234850.GM2545@google.com \
--to=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=zhaoxiu.zeng@gmail.com \
/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).