Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Cc: aou@eecs.berkeley.edu, steve@sk2.org, corbet@lwn.net,
	gregkh@linuxfoundation.org, jpoimboe@redhat.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	tyhicks@canonical.com, clang-built-linux@googlegroups.com,
	palmer@dabbelt.com, paul.walmsley@sifive.com, jkosina@suse.cz,
	tglx@linutronix.de, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] docs: process/index.rst: Fix reference to nonexistent document
Date: Sun, 19 Jul 2020 18:02:14 -0700	[thread overview]
Message-ID: <202007191802.E3B03B06B0@keescook> (raw)
In-Reply-To: <20200718165107.625847-5-dwlsalmeida@gmail.com>

On Sat, Jul 18, 2020 at 01:50:59PM -0300, Daniel W. S. Almeida 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>

Reviewed-by: Kees Cook <keescook@chromium.org>

-- 
Kees Cook

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

       reply	other threads:[~2020-07-20  1:02 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   ` Kees Cook [this message]
2020-07-20 12:39   ` [PATCH] docs: process/index.rst: Fix reference to nonexistent document Stephen Kitt
2020-07-23 20:26   ` Jonathan Corbet

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=202007191802.E3B03B06B0@keescook \
    --to=keescook@chromium.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=clang-built-linux@googlegroups.com \
    --cc=corbet@lwn.net \
    --cc=dwlsalmeida@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=jpoimboe@redhat.com \
    --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