All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Takashi Iwai <tiwai@suse.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	SeongJae Park <sj38.park@gmail.com>
Subject: Re: linux-next: manual merge of the sound tree with the jc_docs tree
Date: Fri, 18 Nov 2016 16:22:18 -0800	[thread overview]
Message-ID: <20161119002218.6k5snf7srxhds4ah@intel.com> (raw)
In-Reply-To: <20161118163312.46505e6f@lwn.net>

On Fri, Nov 18, 2016 at 04:33:12PM -0700, Jonathan Corbet wrote:
> On Mon, 14 Nov 2016 09:01:13 +0100
> Takashi Iwai <tiwai@suse.de> wrote:
> 
> > > 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
> 
> OK, I've done that, so this series will show up in docs-next; hopefully
> the merge conflicts will be resolved in the process.
> 
> I had said that I really wanted to move it all under driver-api and put
> it into that manual, but, looking at what's there, it's not that simple.
> The driver API parts of that manual belong there, but some of the
> information is user-oriented.  A long-term goal is to separate out those
> two types of information so that interested readers can more easily find
> the information relevant to them.  But that won't happen for 4.10..:)  So
> I'll leave things as they are for now.
> 
> (Note also that the driver API manual already has a section on sound
> devices:
> 
> 	http://static.lwn.net/kerneldoc/driver-api/sound.html
> 
> This came from the driver DocBook conversion a while back.  At some point
> we should really pull all that stuff together into a single document).
> 
> Thanks again for doing this conversion,
> 
> jon

Given that there is now a directory for TPM rst documentation do you
still want all changes to your tree or is it sufficient to just cc
linux-doc?

Thanks for fixing the issues!

/Jarkko

  reply	other threads:[~2016-11-19  0:22 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
2016-11-14 16:23       ` Takashi Iwai
2016-11-18 23:33     ` Jonathan Corbet
2016-11-19  0:22       ` Jarkko Sakkinen [this message]
2016-11-19  0:39         ` Jonathan Corbet
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=20161119002218.6k5snf7srxhds4ah@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=corbet@lwn.net \
    --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 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.