[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1433161800-2868-1-git-send-email-vladimir_zapolskiy@mentor.com>
Date: Mon, 1 Jun 2015 15:29:53 +0300
From: Vladimir Zapolskiy <vladimir_zapolskiy@...tor.com>
To: Philipp Zabel <p.zabel@...gutronix.de>,
Heiko Stübner <heiko@...ech.de>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: <linux-kernel@...r.kernel.org>
Subject: [PATCH v5 0/7] misc: sram: minor fixes and clean up
The series contains a number of minor fixes (report correct pool
size, fix ups on error path etc.) and overall driver clean up,
no functional change.
Changes from v4 to v5, thanks to Philipp:
- removed patch v4 3/8 "use phys_addr_t instead of u32 for physical
address" from the series and rebased the rest of the changes;
the patch was removed, because it is helpful only in case,
when SRAM size is larger than 4GiB, which is unlikely
Changes from v3 to v4, thanks to Philipp's review:
- squashed patches v3 1/9 (fix) and 7/9 (clean-up) into v4 1/8
- replaced "0x%llx" with "0x%pa" to display phys_addr_t values
Changes from v2 to v3:
- immediately return -ENOMEM on kmalloc() failure after probe
error path simplification (7/9)
- fixes a variable may be uninitialized warning
Changes from v1 to v2:
- report size of SRAM in decimal format '%zu' instead of '%zx'
- replacement of denominator '1024' to SZ_1K requires explicit
include of linux/sizes.h on some platforms, keep it as a number
Vladimir Zapolskiy (7):
misc: sram: fix enabled clock leak on error path
misc: sram: fix device node reference leak on error
misc: sram: bump error message level on unclean driver unbinding
misc: sram: report correct SRAM pool size
misc: sram: add private struct device and virt_base members
misc: sram: move reserved block logic out of probe function
misc: sram: sort and clean up included headers
drivers/misc/sram.c | 137 +++++++++++++++++++++++++++-------------------------
1 file changed, 72 insertions(+), 65 deletions(-)
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists