From: Jason Gunthorpe <jgg@ziepe.ca>
To: Joel Nider <JOELN@il.ibm.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leon@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH 1/3] docs-rst: infiniband: Convert user verbs doc to rst
Date: Mon, 14 Jan 2019 11:56:13 -0700 [thread overview]
Message-ID: <20190114185613.GF22910@ziepe.ca> (raw)
In-Reply-To: <OFE572E930.5960E029-ONC2258382.00673730-C2258382.0067A91D@notes.na.collabserv.com>
On Mon, Jan 14, 2019 at 08:52:14PM +0200, Joel Nider wrote:
> > > Jonathan/linux-doc: Can you Ack at least the build system parts of
> > > this please? I can take it through the rdma tree, unless you prefer
> > > otherwise?
> >
> > Can I make a request? This appears to be user-oriented documentation; can
> > we please place it into the userspace-api manual, rather than keeping it
> > in its own silo?
>
> I knew someone was going to ask me to do that :-)
> I agree that userspace stuff should all be together, but I guess for
> historical reasons this one stayed in the infiniband section. So if Jason
> is ok with moving the doc, I'll take a look in the morning to see how best
> to work that into the patchset.
I don't mind
Jason
next prev parent reply other threads:[~2019-01-14 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 9:00 updating user verbs documentation Joel Nider
2019-01-14 9:00 ` [PATCH 1/3] docs-rst: infiniband: Convert user verbs doc to rst Joel Nider
2019-01-14 16:56 ` Jason Gunthorpe
2019-01-14 17:34 ` Jonathan Corbet
2019-01-14 18:52 ` Joel Nider
2019-01-14 18:56 ` Jason Gunthorpe [this message]
2019-01-14 9:00 ` [PATCH 2/3] docs-rst: update index file with infiniband docs Joel Nider
2019-01-14 16:54 ` Jason Gunthorpe
2019-01-14 9:00 ` [PATCH 3/3] docs-rst: infiniband: update verbs API details 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=20190114185613.GF22910@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=JOELN@il.ibm.com \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.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).