From: Brian Norris <computersforpeace@gmail.com>
To: <linux-mtd@lists.infradead.org>
Cc: Brian Norris <computersforpeace@gmail.com>
Subject: [PATCH 0/6] mtd: small cleanups
Date: Tue, 20 May 2014 23:16:57 -0700 [thread overview]
Message-ID: <1400653023-25757-1-git-send-email-computersforpeace@gmail.com> (raw)
This series consists of miscellaneous fixes and cleanups, mostly caught through
some sort of static analysis (gcc warnings, sparse, Coverity, etc.).
Brian Norris (6):
mtd: pfow: remove unused variable
mtd: slram: fix unused variable warning
mtd: maps: sc520cdp: fix warnings
mtd: nand_bbt: remove unused variable
mtd: nand_bbt: handle error case for nand_create_badblock_pattern()
mtd: nand: r852: correct write_buf loop bounds
drivers/mtd/devices/slram.c | 4 +---
drivers/mtd/maps/sc520cdp.c | 6 +++---
drivers/mtd/nand/nand_bbt.c | 13 +++++++------
drivers/mtd/nand/r852.c | 6 ++++--
include/linux/mtd/pfow.h | 3 ---
5 files changed, 15 insertions(+), 17 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-05-21 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 6:16 Brian Norris [this message]
2014-05-21 6:16 ` [PATCH 1/6] mtd: pfow: remove unused variable Brian Norris
2014-05-21 6:16 ` [PATCH 2/6] mtd: slram: fix unused variable warning Brian Norris
2014-05-21 6:17 ` [PATCH 3/6] mtd: maps: sc520cdp: fix warnings Brian Norris
2014-05-21 6:17 ` [PATCH 4/6] mtd: nand_bbt: remove unused variable Brian Norris
2014-05-21 6:17 ` [PATCH 5/6] mtd: nand_bbt: handle error case for nand_create_badblock_pattern() Brian Norris
2014-05-21 6:17 ` [PATCH 6/6] mtd: nand: r852: correct write_buf loop bounds Brian Norris
2014-05-28 7:07 ` [PATCH 0/6] mtd: small cleanups Brian Norris
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=1400653023-25757-1-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.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;
as well as URLs for NNTP newsgroup(s).