linux-kernel - [PATCH v2 0/9] misc: sram: minor fixes and clean up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 6 May 2015 14:39:58 +0300
From:	Vladimir Zapolskiy <vladimir_zapolskiy@...tor.com>
To:	Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Heiko Stübner <heiko@...ech.de>,
	Philipp Zabel <p.zabel@...gutronix.de>
CC:	<linux-kernel@...r.kernel.org>
Subject: [PATCH v2 0/9] misc: sram: minor fixes and clean up

The series contains a number of minor fixes (move to phys_addr_t
from u32, fix ups on error path etc.) and overall driver clean up,
no functional change.

Changes since v1:
- 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 (9):
  misc: sram: fix enabled clock leak on error path
  misc: sram: fix device node reference leak on error
  misc: sram: use phys_addr_t instead of u32 for physical address
  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: simplify probe error path
  misc: sram: move reserved block logic out of probe function
  misc: sram: sort and clean up included headers

 drivers/misc/sram.c |  149 +++++++++++++++++++++++++++------------------------
 1 file changed, 80 insertions(+), 69 deletions(-)

-- 
1.7.10.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/