From: Jonathan Corbet <corbet@lwn.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
SeongJae Park <sj38.park@gmail.com>
Subject: Re: linux-next: manual merge of the sound tree with the jc_docs tree
Date: Mon, 14 Nov 2016 09:11:59 -0700 [thread overview]
Message-ID: <20161114091159.670ada51@lwn.net> (raw)
In-Reply-To: <s5ha8d2ebhy.wl-tiwai@suse.de>
On Mon, 14 Nov 2016 09:01:13 +0100
Takashi Iwai <tiwai@suse.de> wrote:
> > Sigh. I'm glad this work is being done, but if we're going to create
> > some coordinated documentation it might be good to involve the docs
> > maintainer when doing it...
>
> Sorry, will put you guys in Cc at the next time (although all
> conversions have been done in the sound tree).
That's kind of my point. The sound tree is not an appropriate place to be
making changes to files like Documentation/index.rst.
> > In this case, I would have liked the chance to comment. This
> > documentation belongs in the driver-api document, not the top-level
> > one. So, in an ideal world, I'd like to see this stuff moved there,
> > preferably with the patches going though the docs tree.
>
> If there needs any other changes, feel free to merge my
> topic/restize-docs branch into yours and keep working there:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> topic/resize-docs
>
> It's based on vanilla 4.9-rc4, so it must be clean to be merged. A
> few misc fixes will come up in for-next branch, but they should be
> harmless to your changes -- at least the api-related changes won't be
> touched.
OK, I'll probably do that; expect me to run a patch by you that moves it
to the proper place in the hierarchy.
Thanks,
jon
next prev parent reply other threads:[~2016-11-14 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 0:15 linux-next: manual merge of the sound tree with the jc_docs tree Stephen Rothwell
2016-11-14 0:56 ` Jonathan Corbet
2016-11-14 8:01 ` Takashi Iwai
2016-11-14 16:11 ` Jonathan Corbet [this message]
2016-11-14 16:23 ` Takashi Iwai
2016-11-18 23:33 ` Jonathan Corbet
2016-11-19 0:22 ` Jarkko Sakkinen
2016-11-19 0:39 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2016-11-14 0:18 Stephen Rothwell
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=20161114091159.670ada51@lwn.net \
--to=corbet@lwn.net \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sj38.park@gmail.com \
--cc=tiwai@suse.de \
/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).