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:	Tue,  1 Sep 2015 20:25:27 +0600
From:	Alexander Kuleshov <kuleshovmail@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Tony Luck <tony.luck@...el.com>,
	Pekka Enberg <penberg@...nel.org>,
	Mel Gorman <mgorman@...e.de>, Xishi Qiu <qiuxishi@...wei.com>,
	Robin Holt <holt@....com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Alexander Kuleshov <kuleshovmail@...il.com>
Subject: [PATCH 0/5 v2] mm/memblock: Introduce memblock_first_region_size() helper

Some architectures (like s390, microblaze and etc...) require size
of the first memory region. This patch set provides new memblock_first_region_size()
helper for this case and change usage of memblock.memory.regions[0].size on
memblock_first_region_size() for the following architectures:

* s390
* microblaze
* arm
* unicore32

Changelog:

v2:

Added changes in the architectures to the patchset.

Alexander Kuleshov (5):
  mm/memblock: Introduce memblock_first_region_size() helper
  s390/setup: use memblock_first_region_size helper
  microblaze/mm: Use memblock_first_region_size() helper
  unicore32/mmu: use memblock_first_region_size() helper
  arm/mmu: Use memblock_first_region_size() helper

 arch/arm/mm/mmu.c         | 2 +-
 arch/microblaze/mm/init.c | 6 +++---
 arch/s390/kernel/setup.c  | 2 +-
 arch/unicore32/mm/mmu.c   | 2 +-
 include/linux/memblock.h  | 1 +
 mm/memblock.c             | 5 +++++
 6 files changed, 12 insertions(+), 6 deletions(-)

-- 
2.5.0

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ