All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerie Aurora <val@versity.com>
To: rpdfs-devel@lists.linux.dev
Cc: Valerie Aurora <val@versity.com>
Subject: [PATCH 3/3] Update documentation
Date: Tue, 24 Feb 2026 17:33:26 +0100	[thread overview]
Message-ID: <20260224163327.2441-4-val@versity.com> (raw)
In-Reply-To: <20260224163327.2441-1-val@versity.com>

---
 docs/development.md | 16 ++++------------
 1 file changed, 4 insertions(+), 12 deletions(-)

diff --git a/docs/development.md b/docs/development.md
index df606b4..02974dd 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -25,9 +25,7 @@ Example invocation:
 In another terminal:
 
 ```
-	$ ./cli/rpdfs-cli debugfs -d 127.0.0.1:8081 -t /tmp/trace_debugfs
-	<1> $ mkfs
-	<1> $ stat
+	# mount -t rpdfs -o mkfs 127.0.0.1:8081 /mnt
 ```
 
 ## Code Layout
@@ -43,18 +41,12 @@ This is all the code that's shared by each utility.  It's not a proper
 library in that it doesn't need to remain API compatible with external
 builds over time.
 
-There's two kinds of shared code.  There's code that can run in either
-userspace or the kernel (block.c) and shared code that only runs in
-userspace (options.c).  It'd probably be worth making this distinction
-more apparent.
-
 **shared/lk/**
 
-This is for userspace implementations of kernel interfaces.  This both
+This is for userspace implementations of kernel interfaces. This both
 lets us use reasonably stand-alone kernel interfaces (list.h) in
-userspace as well as share rpdfs code with the kernel module by
-providing implementations of more complicated runtime services (RCU hash
-tables, work queues).
+userspace by providing implementations of more complicated runtime
+services (RCU hash tables, work queues).
 
 **shared/format-{block,msg,trace}.h**
 
-- 
2.49.0


  parent reply	other threads:[~2026-02-24 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 16:33 [PATCH 0/3] rpdfs-progs: ARM64 support and documentation Valerie Aurora
2026-02-24 16:33 ` [PATCH 1/3] Initial support for ARM64, incompatible with x86_64 Valerie Aurora
2026-02-25 23:36   ` Zach Brown
2026-02-24 16:33 ` [PATCH 2/3] Workaround for short read from io_uring on aarch64 Valerie Aurora
2026-02-25 23:37   ` Zach Brown
2026-02-24 16:33 ` Valerie Aurora [this message]
2026-02-25 23:39   ` [PATCH 3/3] Update documentation Zach Brown
  -- strict thread matches above, loose matches on Subject: below --
2007-08-09 21:23 [PATCH 3/3]: " Ian McDonald
2007-08-09 13:59 Gerrit Renker

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=20260224163327.2441-4-val@versity.com \
    --to=val@versity.com \
    --cc=rpdfs-devel@lists.linux.dev \
    /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.