From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Applied "regmap: Keep regmap_write_bits()" to the regmap tree
Date: Wed, 2 Mar 2016 12:07:17 +0900 [thread overview]
Message-ID: <20160302030717.GT18327@sirena.org.uk> (raw)
In-Reply-To: <20160301181146.48689326@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
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@kernel.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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-02 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 14:02 Mark Brown
2016-02-29 22:00 ` Stephen Rothwell
2016-03-01 2:25 ` Mark Brown
2016-03-01 7:11 ` Stephen Rothwell
2016-03-02 3:07 ` Mark Brown [this message]
2016-03-02 4:36 ` Mark Brown
2016-03-02 5:25 ` 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=20160302030717.GT18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®