linux-kernel - Re: Applied "regmap: Keep regmap_write

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]

Message-ID: <20160302030717.GT18327@sirena.org.uk>
Date:	Wed, 2 Mar 2016 12:07:17 +0900
From:	Mark Brown <broonie@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Applied "regmap: Keep regmap_write_bits()" to the regmap tree

On Tue, Mar 01, 2016 at 06:11:46PM +1100, Stephen Rothwell wrote:
> On Tue, 1 Mar 2016 11:25:44 +0900 Mark Brown <broonie@...nel.org> wrote:

> > It'll sort itself out by the time things get merged down into Linus'
> > tree, that's why I did it as a revert rather than just dropping the
> > patch.  Linus generally takes regmap before ALSA.

> Well, I have the sound trees before the regmap tree.  I also dislike

Oh, that's a bit surprising.

> having these sort of dependencies between trees.  What happens if Linus
> does merge the sound tree first?

> You already merged part of the regmap tree into the sound-asoc tree,
> why not do that again with the fix?

I tend to treat things that are real fixes as opposed to things that
are test only fixes a bit differently to each other - lots of cross
merges get messy, if it's not going to hit someone doing something in a
real system I tend to not worry about it too much.

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