linux-kernel - Re: linux-next: lots of merges in the sound-asoc tree

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] [day] [month] [year] [list]

Message-ID: <20180213114210.GA5988@sirena.org.uk>
Date:   Tue, 13 Feb 2018 11:42:10 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Subject: Re: linux-next: lots of merges in the sound-asoc tree

On Tue, Feb 13, 2018 at 09:38:57AM +1100, Stephen Rothwell wrote:

> I know that you usually like to keep one topic branch per soc and then
> merge them all, but currently your tree seems to only contain a couple
> logical changes (platform to component and codec to component), so
> surely that could have been done in (maybe) 2 topic branches and saved
> large number of very small branches (often a single commit) and a large
> number of merges.

If you look at the changes that are per branch (one series is on a
single branch due to dependencies and a lower change rate) they're often
relatively large and likely to conflict with further development that
gets done.  This also lets me drop anything that causes problems much
more easily.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)