linux-kernel - [PATCH v1 0/2] drivers/base/memory: clarify some memory block properties

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]

Message-Id: <20210201105158.6393-1-david@redhat.com>
Date:   Mon,  1 Feb 2021 11:51:56 +0100
From:   David Hildenbrand <david@...hat.com>
To:     linux-kernel@...r.kernel.org
Cc:     linux-mm@...ck.org, David Hildenbrand <david@...hat.com>
Subject: [PATCH v1 0/2] drivers/base/memory: clarify some memory block properties

Let's update parts of our documentation for
/sys/devices/system/memory/memoryX/ properties, especially stating which
properties are nowadays legacy interfaces.

David Hildenbrand (2):
  drivers/base/memory: don't store phys_device in memory blocks
  Documentation: sysfs/memory: clarify some memory block device
    properties

 .../ABI/testing/sysfs-devices-memory          | 58 ++++++++++++-------
 .../admin-guide/mm/memory-hotplug.rst         | 20 +++----
 drivers/base/memory.c                         | 23 +++-----
 include/linux/memory.h                        |  3 +-
 4 files changed, 56 insertions(+), 48 deletions(-)

-- 
2.29.2