linux-kernel - Re: linux-next: manual merge of the sound tree with the jc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 18 Nov 2016 16:22:18 -0800
From:   Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Takashi Iwai <tiwai@...e.de>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        SeongJae Park <sj38.park@...il.com>
Subject: Re: linux-next: manual merge of the sound tree with the jc_docs tree

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@...e.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