From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: devel@driverdev.osuosl.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 3/5] ncpfs: remove Documentation
Date: Fri, 1 Jun 2018 20:45:45 +0200 [thread overview]
Message-ID: <20180601184547.20213-4-gregkh@linuxfoundation.org> (raw)
In-Reply-To: <20180601184547.20213-1-gregkh@linuxfoundation.org>
No need for any more ncpfs documentation around given that the
filesystem is now removed.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Documentation/filesystems/00-INDEX | 2 --
Documentation/filesystems/ncpfs.txt | 12 ------------
2 files changed, 14 deletions(-)
delete mode 100644 Documentation/filesystems/ncpfs.txt
diff --git a/Documentation/filesystems/00-INDEX b/Documentation/filesystems/00-INDEX
index b7bd6c9009cc..5f305a2af852 100644
--- a/Documentation/filesystems/00-INDEX
+++ b/Documentation/filesystems/00-INDEX
@@ -89,8 +89,6 @@ locks.txt
- info on file locking implementations, flock() vs. fcntl(), etc.
mandatory-locking.txt
- info on the Linux implementation of Sys V mandatory file locking.
-ncpfs.txt
- - info on Novell Netware(tm) filesystem using NCP protocol.
nfs/
- nfs-related documentation.
nilfs2.txt
diff --git a/Documentation/filesystems/ncpfs.txt b/Documentation/filesystems/ncpfs.txt
deleted file mode 100644
index 5af164f4b37b..000000000000
--
2.17.1
next prev parent reply other threads:[~2018-06-01 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 18:45 [PATCH 0/5] staging: remove ncpfs and ipx code Greg Kroah-Hartman
2018-06-01 18:45 ` [PATCH 1/5] staging: ncpfs: delete it Greg Kroah-Hartman
2018-06-01 18:45 ` [PATCH 2/5] ncpfs: remove compat functionality Greg Kroah-Hartman
2018-06-01 18:45 ` Greg Kroah-Hartman [this message]
2018-06-01 18:45 ` [PATCH 4/5] ncpfs: remove uapi .h files Greg Kroah-Hartman
2018-06-01 18:45 ` [PATCH 5/5] staging: ipx: delete it from the tree Greg Kroah-Hartman
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=20180601184547.20213-4-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).