linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Slaby <jirislaby@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Wan Jiabing <wanjiabing@vivo.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	kael_w@qq.com
Subject: Re: [PATCH] docs: serial: fix a reference file name in driver.rst
Date: Wed, 16 Mar 2022 15:43:00 -0600	[thread overview]
Message-ID: <87k0ctshej.fsf@meer.lwn.net> (raw)
In-Reply-To: <af1c7dd1-d86d-d737-643e-1f20a19c3890@kernel.org>

Jiri Slaby <jirislaby@kernel.org> writes:

> Returning to this: staring into Documentation/index.rst and 
> Documentation/driver-api/index.rst. Looking at documents/paths they 
> reference, I still don't quite understand what is the rule to put the 
> stuff to either of them.
>
> What I used to decide to put the tty stuff to the root is that it's not 
> only driver-api documented there. It documents also tty internals and 
> implementation of some line disciplines.
>
> So, now I'm confused why it does NOT belong to the root.

My thinking is: for the same reason that drivers/tty is not in the root.

I've been pushing for some time to get our documentation organized for
the readers, which means arranging things in terms of the expected
audience.  Much of what's in Documentation/tty looks like driver-api
stuff, so that's where I would like it to be.  If you have material for
other audiences, perhaps that material should go into a different book.

When I started doing this, "ls Documentation" would scroll on for many
pages.  We've been slowly moving away from that directory as an
unorganized dumping ground, but there is still a ways to go.

Thanks,

jon

      reply	other threads:[~2022-03-16 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 10:03 [PATCH] docs: serial: fix a reference file name in driver.rst Wan Jiabing
2022-03-07  6:41 ` Jiri Slaby
2022-03-11 21:06   ` Jonathan Corbet
2022-03-12  6:59     ` Greg Kroah-Hartman
2022-03-14  6:16       ` Jiri Slaby
2022-03-16  7:49         ` Jiri Slaby
2022-03-16 21:43           ` 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=87k0ctshej.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kael_w@qq.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wanjiabing@vivo.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).