linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huijin Park <huijin.park@samsung.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	Huijin Park <huijin.park@samsung.com>,
	bbanghj.park@gmail.com, Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH v3] mtd: change len type from signed to unsigned type
Date: Wed, 28 Nov 2018 23:19:51 -0500	[thread overview]
Message-ID: <1543465191-2100-1-git-send-email-huijin.park@samsung.com> (raw)
In-Reply-To: CGME20181129042000eucas1p19a67f367e084ed5d5f37f72e57eb98d5@eucas1p1.samsung.com

From: "huijin.park" <huijin.park@samsung.com>

Callers of erase_write() always pass an unsigned int.
So this patch avoids a cast to an int.

Signed-off-by: huijin.park <huijin.park@samsung.com>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>

---

Changes since v1:
 * Made commit message more clear.
Changes since v2:
 * Made commit message more clear.
---
 drivers/mtd/mtdblock.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/mtd/mtdblock.c b/drivers/mtd/mtdblock.c
index a5b1933..b2d5ed1 100644
--- a/drivers/mtd/mtdblock.c
+++ b/drivers/mtd/mtdblock.c
@@ -56,7 +56,7 @@ struct mtdblk_dev {
  */
 
 static int erase_write (struct mtd_info *mtd, unsigned long pos,
-			int len, const char *buf)
+			unsigned int len, const char *buf)
 {
 	struct erase_info erase;
 	size_t retlen;
-- 
1.7.9.5


       reply	other threads:[~2018-11-29  4:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20181129042000eucas1p19a67f367e084ed5d5f37f72e57eb98d5@eucas1p1.samsung.com>
2018-11-29  4:19 ` Huijin Park [this message]
2018-12-03  7:51   ` [v3] mtd: change len type from signed to unsigned type Boris Brezillon

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=1543465191-2100-1-git-send-email-huijin.park@samsung.com \
    --to=huijin.park@samsung.com \
    --cc=bbanghj.park@gmail.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=miquel.raynal@bootlin.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).