All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Palmer via B4 Relay
	<devnull+daniel.palmer.sony.com@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel Palmer <daniel.palmer@sony.com>
Subject: Re: [PATCH] doc: Remove misleading reference to brd in dax.rst
Date: Wed, 25 Jun 2025 12:49:38 -0600	[thread overview]
Message-ID: <87sejn8xml.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250610-fixdasrstbrd20250610-v1-1-4abe3b7f381a@sony.com>

Daniel Palmer via B4 Relay <devnull+daniel.palmer.sony.com@kernel.org>
writes:

> From: Daniel Palmer <daniel.palmer@sony.com>
>
> brd hasn't supported DAX for a long time but dax.rst
> still suggests it as an example of how to write a DAX
> supporting block driver.
>
> Remove the reference, confuse less people.
>
> Fixes: 7a862fbbdec6 ("brd: remove dax support")
> Signed-off-by: Daniel Palmer <daniel.palmer@sony.com>
> ---
>  Documentation/filesystems/dax.rst | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/filesystems/dax.rst b/Documentation/filesystems/dax.rst
> index 08dd5e254cc5..5b283f3d1eb1 100644
> --- a/Documentation/filesystems/dax.rst
> +++ b/Documentation/filesystems/dax.rst
> @@ -206,7 +206,6 @@ stall the CPU for an extended period, you should also not attempt to
>  implement direct_access.
>  
>  These block devices may be used for inspiration:
> -- brd: RAM backed block device driver
>  - pmem: NVDIMM persistent memory driver

Applied, thanks.

jon

      reply	other threads:[~2025-06-25 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 23:37 [PATCH] doc: Remove misleading reference to brd in dax.rst Daniel Palmer
2025-06-09 23:37 ` Daniel Palmer via B4 Relay
2025-06-25 18:49 ` Jonathan Corbet [this message]

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=87sejn8xml.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=daniel.palmer@sony.com \
    --cc=devnull+daniel.palmer.sony.com@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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 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.