From: Mike Rapoport <rppt@linux.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Joel Nider <JOELN@il.ibm.com>, Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2 2/2] docs-rst: userspace: update verbs API details
Date: Thu, 17 Jan 2019 02:06:16 +0200 [thread overview]
Message-ID: <20190117000615.GA18089@rapoport-lnx> (raw)
In-Reply-To: <20190115143859.4cbd5d9c@lwn.net>
Hi Jon,
On Tue, Jan 15, 2019 at 02:38:59PM -0700, Jonathan Corbet wrote:
> On Tue, 15 Jan 2019 22:37:01 +0200
>
> I'd rather see you put the new stuff under Documentation/driver-api, either
> in a standalone file or in a new subdirectory.
>
> Thanks for your patience with this! We really do want people to contribute
> more documentation, and I feel bad when it seems like I'm making it
> harder. My hope is that it will pay off in the long run; I think there are
> signs already that this is happening.
I believe its worth adding Documentation/doc-guide/where-to-put-stuff.rst
with at least basic guidelines for the desired organization of
Documentation/.
> Thanks,
>
> jon
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-01-17 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 10:26 docs-rst: update infiniband uverbs doc Joel Nider
2019-01-15 10:26 ` [PATCH v2 1/2] docs-rst: Convert user verbs doc to rst Joel Nider
2019-01-15 15:14 ` Jason Gunthorpe
2019-01-15 18:02 ` Jonathan Corbet
2019-01-15 20:41 ` Joel Nider
2019-01-15 10:26 ` [PATCH v2 2/2] docs-rst: userspace: update verbs API details Joel Nider
2019-01-15 15:31 ` Matthew Wilcox
2019-01-15 16:29 ` Joel Nider
2019-01-15 18:08 ` Jonathan Corbet
2019-01-15 20:37 ` Joel Nider
2019-01-15 21:38 ` Jonathan Corbet
2019-01-17 0:06 ` Mike Rapoport [this message]
2019-01-17 6:33 ` Joel Nider
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=20190117000615.GA18089@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=JOELN@il.ibm.com \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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.