All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>
Subject: [PATCH v1 0/2] drivers/base/memory: clarify some memory block properties
Date: Mon,  1 Feb 2021 11:51:56 +0100	[thread overview]
Message-ID: <20210201105158.6393-1-david@redhat.com> (raw)

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


             reply	other threads:[~2021-02-01 10:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 10:51 David Hildenbrand [this message]
2021-02-01 10:51 ` [PATCH v1 1/2] drivers/base/memory: don't store phys_device in memory blocks David Hildenbrand
2021-02-01 13:00   ` kernel test robot
2021-02-01 13:00     ` kernel test robot
2021-02-01 13:27     ` David Hildenbrand
2021-02-01 13:27       ` David Hildenbrand
2021-02-01 15:58   ` Michal Hocko
2021-02-01 10:51 ` [PATCH v1 2/2] Documentation: sysfs/memory: clarify some memory block device properties David Hildenbrand
2021-02-01 16:00   ` Michal Hocko

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=20210201105158.6393-1-david@redhat.com \
    --to=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.