linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Cc: aou@eecs.berkeley.edu, steve@sk2.org, keescook@chromium.org,
	jkosina@suse.cz, gregkh@linuxfoundation.org,
	paul.walmsley@sifive.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, tyhicks@canonical.com,
	clang-built-linux@googlegroups.com, palmer@dabbelt.com,
	jpoimboe@redhat.com, tglx@linutronix.de,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] docs: process/index.rst: Fix reference to nonexistent document
Date: Thu, 23 Jul 2020 14:26:44 -0600	[thread overview]
Message-ID: <20200723142644.5dd89bd4@lwn.net> (raw)
In-Reply-To: <20200718165107.625847-5-dwlsalmeida@gmail.com>

On Sat, 18 Jul 2020 13:50:59 -0300
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com> wrote:

> From: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
> 
> Fix the following warning:
> 
> WARNING: toctree contains reference to nonexistent document
> 'process/unaligned-memory-access'
> 
> The path to the document was wrong.
> 
> Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
> ---
>  Documentation/process/index.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/index.rst b/Documentation/process/index.rst
> index f07c9250c3acb..dd231ffc8422d 100644
> --- a/Documentation/process/index.rst
> +++ b/Documentation/process/index.rst
> @@ -32,7 +32,7 @@ Below are the essential guides that every developer should read.
>     kernel-enforcement-statement
>     kernel-driver-statement
>  
> -Other guides to the community that are of interest to most developers are: 
> +Other guides to the community that are of interest to most developers are:
>  
>  .. toctree::
>     :maxdepth: 1
> @@ -61,7 +61,7 @@ lack of a better place.
>     botching-up-ioctls
>     clang-format
>     ../riscv/patch-acceptance
> -   unaligned-memory-access
> +   ../core-api/unaligned-memory-access

Applied, but the right solution is probably just to list it in the
core-api book rather than here.

Thanks,

jon

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2020-07-23 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200718165107.625847-1-dwlsalmeida@gmail.com>
     [not found] ` <20200718165107.625847-5-dwlsalmeida@gmail.com>
2020-07-20  1:02   ` [PATCH] docs: process/index.rst: Fix reference to nonexistent document Kees Cook
2020-07-20 12:39   ` Stephen Kitt
2020-07-23 20:26   ` 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=20200723142644.5dd89bd4@lwn.net \
    --to=corbet@lwn.net \
    --cc=aou@eecs.berkeley.edu \
    --cc=clang-built-linux@googlegroups.com \
    --cc=dwlsalmeida@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=jpoimboe@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=steve@sk2.org \
    --cc=tglx@linutronix.de \
    --cc=tyhicks@canonical.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;
as well as URLs for NNTP newsgroup(s).