From: Thomas Preston <thomas.preston@codethink.co.uk>
To: anna.schumaker@netapp.com, jlayton@kernel.org,
bfields@fieldses.org, linux-nfs@vger.kernel.org
Cc: ts001-upstream@lists.codethink.co.uk,
Thomas Preston <thomas.preston@codethink.co.uk>
Subject: [PATCH 0/1] SUNRPC: Allow /proc entries without CONFIG_SUNRPC_DEBUG
Date: Tue, 20 Nov 2018 17:59:29 +0000 [thread overview]
Message-ID: <20181120175930.27853-1-thomas.preston@codethink.co.uk> (raw)
Hello,
We have a patch which adds sunrpc /proc entries without having to enable the
full SUNRPC debug, which we found useful. Tested on NVIDIA Tegra30.
Many thanks,
Thomas
Ben Dooks (1):
SUNRPC: allow /proc entries without CONFIG_SUNRPC_DEBUG
net/sunrpc/Kconfig | 7 +++++++
net/sunrpc/xprtsock.c | 6 +++---
2 files changed, 10 insertions(+), 3 deletions(-)
--
2.11.0
next reply other threads:[~2018-11-20 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 17:59 Thomas Preston [this message]
2018-11-20 17:59 ` [PATCH 1/1] SUNRPC: allow /proc entries without CONFIG_SUNRPC_DEBUG Thomas Preston
2018-11-27 21:29 ` Schumaker, Anna
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=20181120175930.27853-1-thomas.preston@codethink.co.uk \
--to=thomas.preston@codethink.co.uk \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ts001-upstream@lists.codethink.co.uk \
/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