From: Stephen Kitt <steve@sk2.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: sysctl/kernel: document unaligned controls
Date: Fri, 15 May 2020 20:36:01 +0200 [thread overview]
Message-ID: <20200515203601.401a46a9@heffalump.sk2.org> (raw)
In-Reply-To: <20200515112735.67ee1148@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Fri, 15 May 2020 11:27:35 -0600, Jonathan Corbet <corbet@lwn.net> wrote:
> On Fri, 15 May 2020 18:04:06 +0200
> Stephen Kitt <steve@sk2.org> wrote:
>
> > diff --git a/Documentation/index.rst b/Documentation/index.rst
> > index 9599c0f3eea8..17c38d899572 100644
> > --- a/Documentation/index.rst
> > +++ b/Documentation/index.rst
> > @@ -143,6 +143,7 @@ Architecture-agnostic documentation
> > :maxdepth: 2
> >
> > asm-annotations
> > + unaligned-memory-access
> >
> > Architecture-specific documentation
> > -----------------------------------
> > diff --git a/Documentation/unaligned-memory-access.txt
> > b/Documentation/unaligned-memory-access.rst similarity index 100%
> > rename from Documentation/unaligned-memory-access.txt
> > rename to Documentation/unaligned-memory-access.rst
>
> Adding this to the toctree is great, but I'd just as soon not leave it in
> the top-level directory while we do that. Since you're renaming it
> anyway, can you move it into process/? It's not a perfect fit, but that's
> where that type of material has been going so far.
I can indeed. Should it still be listed in the main toctree, or in the
process toctree?
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-15 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 16:04 [PATCH] docs: sysctl/kernel: document unaligned controls Stephen Kitt
2020-05-15 17:27 ` Jonathan Corbet
2020-05-15 18:36 ` Stephen Kitt [this message]
2020-05-15 21:17 ` Stephen Kitt
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=20200515203601.401a46a9@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@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).