From: Benjamin Romer <benjamin.romer@unisys.com>
To: <gregkh@linuxfoundation.org>, <sparmaintainer@unisys.com>,
<linux-kernel@vger.kernel.org>, <jkc@redhat.com>,
<devel@driverdev.osuosl.org>
Subject: [PATCH 0/7] staging: unisys: cleanup proc entries in uislib
Date: Mon, 12 May 2014 12:38:28 -0400 [thread overview]
Message-ID: <1399912715-16142-1-git-send-email-benjamin.romer@unisys.com> (raw)
This patch series removes old and redundant proc entries from the uislib
module, and moves the remaining entries to debugfs. The removed entries are
from unit testing of the module and are no longer used. The information in the
vbus directory was redundant, so the directory and entries are removed. The
remaining entries are only interesting when debugging, and are not used by any
user space program, so debugfs is the right place for them.
next reply other threads:[~2014-05-12 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 16:38 Benjamin Romer [this message]
2014-05-12 16:38 ` [PATCH 1/7] staging: unisys: remove testing proc interfaces from uislib Benjamin Romer
2014-05-12 16:38 ` [PATCH 2/7] staging: unisys: move uislib/platform proc entry to debugfs Benjamin Romer
2014-05-18 16:49 ` Greg KH
2014-05-19 14:42 ` Romer, Benjamin M
2014-05-19 19:57 ` Dan Carpenter
2014-05-20 1:09 ` Greg KH
2014-05-20 13:20 ` Romer, Benjamin M
2014-05-12 16:38 ` [PATCH 3/7] staging: unisys: move uislib/cycles_before_wait " Benjamin Romer
2014-05-12 16:38 ` [PATCH 4/7] staging: unisys: move uislib/smart_wakeup " Benjamin Romer
2014-05-12 16:38 ` [PATCH 5/7] staging: unisys: remove functions made redundant in uislib.c Benjamin Romer
2014-05-12 16:38 ` [PATCH 6/7] staging: unisys: move uislib/info proc entry to debugfs Benjamin Romer
2014-05-12 16:38 ` [PATCH 7/7] staging: unisys: remove remaining proc directory entries Benjamin Romer
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=1399912715-16142-1-git-send-email-benjamin.romer@unisys.com \
--to=benjamin.romer@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkc@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparmaintainer@unisys.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
all inboxes | Powered by JetHome®