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:   Sun, 13 Nov 2016 17:56:28 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Takashi Iwai <tiwai@...e.de>, linux-next@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        SeongJae Park <sj38.park@...il.com>
Subject: Re: linux-next: manual merge of the sound tree with the jc_docs
 tree

On Mon, 14 Nov 2016 11:15:53 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Today's linux-next merge of the sound tree got a conflict in:
> 
>   Documentation/index.rst
> 
> between commits:
> 
>   799a545bb938 ("tpm: move documentation under Documentation/security")
>   ba42c574fc8b ("Documentation: Add HOWTO Korean translation into rst based build system")
> 
> from the jc_docs tree and commit:
> 
>   8551914a5e19 ("ALSA: doc: ReSTize alsa-driver-api document")
> 
> from the sound tree.

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

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.

(Thanks, Stephen, for fixing it up).

jon