From: David Howells <dhowells@redhat.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: dhowells@redhat.com,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir
Date: Wed, 19 Jun 2019 14:39:10 +0100 [thread overview]
Message-ID: <11422.1560951550@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190619072218.4437f891@coco.lan>
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> > > -Documentation/nommu-mmap.rst
> > > +Documentation/driver-api/nommu-mmap.rst
Why is this moving to Documentation/driver-api? It's less to do with drivers
than with the userspace mapping interface. Documentation/vm/ would seem a
better home.
Or should we institute a Documentation/uapi/? Though that might be seen to
overlap with man2. Actually, should this be in man7?
David
next prev parent reply other threads:[~2019-06-19 13:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1560890771.git.mchehab+samsung@kernel.org>
2019-06-18 20:53 ` Mauro Carvalho Chehab
2019-06-19 8:24 ` Thierry Reding
2019-06-19 9:05 ` Daniel Vetter
2019-06-19 10:22 ` Mauro Carvalho Chehab
2019-06-19 10:42 ` Peter Zijlstra
2019-06-19 13:07 ` Mauro Carvalho Chehab
2019-06-19 14:13 ` Jonathan Corbet
2019-06-19 13:39 ` David Howells [this message]
2019-06-19 14:15 ` Mauro Carvalho Chehab
2019-06-19 14:54 ` Jonathan Corbet
2019-06-19 15:52 ` Jani Nikula
2019-06-19 15:54 ` Mauro Carvalho Chehab
2019-06-19 11:43 ` Peter Zijlstra
2019-06-19 11:45 ` Peter Zijlstra
2019-06-19 11:50 ` Peter Zijlstra
2019-06-19 12:50 ` Andrea Parri
[not found] <cover.1560891322.git.mchehab+samsung@kernel.org>
2019-06-18 21:05 ` Mauro Carvalho Chehab
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=11422.1560951550@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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