From: Greg KH <gregkh@linuxfoundation.org>
To: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: mpe@ellerman.id.au, mahesh@linux.vnet.ibm.com,
hbathini@linux.ibm.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 1/6] Documentation/ABI: add ABI documentation for /sys/kernel/fadump_*
Date: Fri, 6 Dec 2019 13:47:07 +0100 [thread overview]
Message-ID: <20191206124707.GC1360047@kroah.com> (raw)
In-Reply-To: <20191206122434.29587-2-sourabhjain@linux.ibm.com>
On Fri, Dec 06, 2019 at 05:54:29PM +0530, Sourabh Jain wrote:
> Add missing ABI documentation for existing FADump sysfs files.
>
> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
> ---
> Documentation/ABI/testing/sysfs-kernel-fadump_enabled | 7 +++++++
> Documentation/ABI/testing/sysfs-kernel-fadump_registered | 8 ++++++++
> Documentation/ABI/testing/sysfs-kernel-fadump_release_mem | 8 ++++++++
> .../ABI/testing/sysfs-kernel-fadump_release_opalcore | 7 +++++++
> 4 files changed, 30 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump_enabled
> create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump_registered
> create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump_release_mem
> create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump_release_opalcore
>
> diff --git a/Documentation/ABI/testing/sysfs-kernel-fadump_enabled b/Documentation/ABI/testing/sysfs-kernel-fadump_enabled
> new file mode 100644
> index 000000000000..f73632b1c006
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-kernel-fadump_enabled
> @@ -0,0 +1,7 @@
> +What: /sys/kernel/fadump_enabled
Ugh, no wonder no one wanted to document these, that would have been
noticed right away :(
greg k-h
next prev parent reply other threads:[~2019-12-06 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 12:24 [PATCH v4 0/6] reorganize and add FADump sysfs files Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 1/6] Documentation/ABI: add ABI documentation for /sys/kernel/fadump_* Sourabh Jain
2019-12-06 12:47 ` Greg KH [this message]
2019-12-06 12:24 ` [PATCH v4 2/6] sysfs: wrap __compat_only_sysfs_link_entry_to_kobj function to change the symlink name Sourabh Jain
2019-12-06 12:46 ` Greg KH
2019-12-06 18:27 ` Sourabh Jain
2019-12-06 19:14 ` Greg KH
2019-12-07 3:21 ` Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 3/6] powerpc/fadump: reorganize /sys/kernel/fadump_* sysfs files Sourabh Jain
2019-12-06 12:45 ` Greg KH
2019-12-06 19:13 ` Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 4/6] powerpc/powernv: move core and fadump_release_opalcore under new kobject Sourabh Jain
2019-12-06 12:48 ` Greg KH
2019-12-06 19:16 ` Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 5/6] Documentation/ABI: mark /sys/kernel/fadump_* sysfs files deprecated Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 6/6] powerpc/fadump: sysfs for fadump memory reservation Sourabh Jain
2019-12-06 12:48 ` Greg KH
2019-12-06 19:19 ` Sourabh Jain
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=20191206124707.GC1360047@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=hbathini@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sourabhjain@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).